US20060255929A1 - Threat scanning machine management system - Google Patents

Threat scanning machine management system Download PDF

Info

Publication number
US20060255929A1
US20060255929A1 US11/493,012 US49301206A US2006255929A1 US 20060255929 A1 US20060255929 A1 US 20060255929A1 US 49301206 A US49301206 A US 49301206A US 2006255929 A1 US2006255929 A1 US 2006255929A1
Authority
US
United States
Prior art keywords
threat
threat scanning
scanning machine
management
module
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/493,012
Inventor
Joseph Zanovitch
Susan Douglas
Michael Heaton
Tonya Bender
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US11/493,012 priority Critical patent/US20060255929A1/en
Publication of US20060255929A1 publication Critical patent/US20060255929A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Definitions

  • the present invention relates generally to system management, and, more particularly, to the management of threat scanning machines.
  • Threat scanning machines are often employed in locations where safety and security are at issue.
  • Transportation facilities for example, airports, train stations, seaports, and the like, may employ threat scanning machines to detect security threats within passenger or freight baggage.
  • Other facilities such as office buildings, government buildings, court houses, museums and the like may employ threat scanning machines to detect restricted items being carried by a person seeking entry to the facility.
  • a threat scanning machine refers to any device capable of detecting an object defined as a threat.
  • a threat can be anything that is restricted from being brought aboard a vehicle, into a building or into an area.
  • Threat scanning machines may be of different make and model, including carry-on bag scanning machines, checked-bag scanning machines, walk-through metal detectors, x-rays, computerized tomography devices, magnetic resonance imaging devices, and the like, thus requiring individualized maintenance and control of each machine's software and data components.
  • the task of individually maintaining and controlling each machine may be time consuming, prone to error and expensive. For example, when supervisor attention is required at a particular machine, the supervisor must physically go to the machine, assess the situation and provide guidance to the threat scanning machine operator.
  • the software in an existing threat scanning machine needs to be upgraded, the media containing the upgrade may be required to be carried from machine to machine in order to perform the upgrade.
  • the diversity of threat scanning machine types and the varied locations of threat scanning machines pose obstacles to the efficient management of the threat scanning machines.
  • the threat scanning machines are connected to a communication network.
  • One or more control center computers are connected to the communication network.
  • the threat scanning machines possibly of different make and model, are adapted with hardware and software to allow them to communicate over the network with the control center computer.
  • the control center computer is adapted with software and/or hardware to control and manage threat scanning machines.
  • t-he control computer can transmit data, such as, for example, operational software and threat profiles to the threat scanning machine; and the threat scanning machines may transmit data, such as, for example, images and performance data to the control computer.
  • a supervisor may view the images or performance data of a threat scanning machine remotely on the control center computer, assess the situation and assist the threat scanning machine operator remotely, thereby permitting the supervisor to manage multiple threat scanning machines in an efficient manner.
  • the threat scanning machine management system may be dynamically configurable, the network may be a wireless network, and the control center computer may be a portable device, thus permitting a superior to manage the threat scanning machines while remaining mobile.
  • FIG. 1 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system
  • FIG. 2 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system showing the control centers connected to a threat scanning machine in accordance with the present invention
  • FIG. 3 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system showing the details of an exemplary threat scanning machine in accordance with the present invention
  • FIG. 4 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system showing the details of an exemplary control center in accordance with the present invention
  • FIG. 5 is a functional block diagram of an exemplary embodiment of the logical functions of an exemplary threat management module in accordance with the present invention
  • FIG. 6 is a functional block diagram of an exemplary embodiment of a remote management module in accordance with the present invention.
  • FIG. 7 is a functional block diagram of an exemplary embodiment of a maintenance server module in accordance with the present invention.
  • FIG. 8 is a functional block diagram of an exemplary embodiment of a control center database and web service connections in accordance with the present invention.
  • FIG. 9 is a functional block diagram of an exemplary control and maintenance system showing a web browser connection in accordance with the present invention.
  • FIG. 10 is a functional block diagram of an exemplary threat scanning machine architecture in accordance with the present invention.
  • FIG. 11 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing an exemplary approach to network security in accordance with the present invention
  • FIG. 12 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary security components in accordance with the present invention
  • FIGS. 13A and 13B are a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary alternative approaches to the network connection of security equipment in accordance with the present invention
  • FIG. 14 is a functional block diagram of an exemplary message interface between a threat scanning machine and the threat scanning machine management system in accordance with the present invention.
  • FIG. 15 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the main menu screen
  • FIG. 16 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Remote Management menu
  • FIG. 17 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Threat Management menu
  • FIG. 18 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Maintenance Server menu
  • FIG. 19 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Threat Image Projection (TIP) Management menu;
  • TIP Threat Image Projection
  • FIG. 20 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing Event information
  • FIG. 21 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing User Administration data
  • FIG. 22 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Fault Reporting selection dialog
  • FIG. 23 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Report Filter selection dialog
  • FIG. 24 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing System Administration data
  • FIG. 25 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a download schedule
  • FIG. 26 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the System Administration screen
  • FIG. 27 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Throughput Report
  • FIG. 28 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Personnel Report
  • FIG. 29 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Current Alarm Report
  • FIG. 30 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing an Historical Bag/Threat Information Report
  • FIG. 31 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Threat Type Information Report
  • FIG. 32 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing an All Actions Taken Information Report
  • FIG. 33 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a File Management Report
  • FIG. 34 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Profile Management Report
  • FIG. 35 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Download Management Report
  • FIG. 36 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a TIP Image Management Report
  • FIG. 37 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Fault Report.
  • FIG. 38 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface adapted for use on a handheld or portable computer showing the main menu screen.
  • the various components of the system can be located at distant portions of a distributed network, such as a telecommunications network and/or the Internet or within a dedicated communications network.
  • a distributed network such as a telecommunications network and/or the Internet or within a dedicated communications network.
  • the components of the threat scanning machine and the command and control center, respectively can be combined into one or more devices or collocated on a particular note of a distributed network, such as a telecommunications network.
  • the components of the communications network can be arranged at any location within the distributed network without affecting the operation of the system.
  • the exemplary embodiments shown provide a layout of the system in which the subsystems (i.e. Threat Management, Remote Management, and Maintenance Server) are shown separately for conceptual clarity and for illustrative purposes in both the threat scanning machines and the command and control center.
  • the subsystems i.e. Threat Management, Remote Management, and Maintenance Server
  • FIG. 1 the exemplary embodiments shown provide a layout of the system in which the subsystems (i.e. Threat Management, Remote Management, and Maintenance Server) are shown separately for conceptual clarity and for illustrative purposes in both the threat scanning machines and the command and control center.
  • the subsystems i.e. Threat Management, Remote Management, and Maintenance Server
  • the various links connecting the elements can be wired or wireless links, or a combination thereof, or any known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements.
  • FIG. 1 shows a functional block diagram of an exemplary embodiment of a threat scanning machine management system 100 .
  • a command and control center 102 forms a top level of a system hierarchy and is interconnected by a network 112 to a next level comprising command and control centers 104 .
  • a command and control center 104 is interconnected with a threat scanning machine 106 by the network 112 .
  • a command and control center 104 is interconnected to command and control center 108 and to command and control center 110 via the network 112 .
  • a command and control center 110 is interconnected to one or more threat scanning machines 106 via the network 112 .
  • the threat scanning machine management system 100 shown in FIG. 1 represents, for purposes of illustration, an exemplary configuration of command and control centers connected to each other and to threat scanning machines. However, it should be appreciated that the system 100 can be configured in order to be adaptable to various contemplated uses of the present invention.
  • the configuration of the system 100 may be static or dynamic depending on contemplated uses of the invention.
  • a transportation facility may have an existing network (not shown), and in such a case, the threat scanning machine management system 100 may be adapted to the existing network.
  • a new network can be installed for the threat scanning machine management system 100 to communicate over.
  • any communications medium that allows the threat scanning machines and the control centers to communicate may be used with equal success.
  • the command and control centers and the threat scanning machines communicate over the network 112 using standard protocols common in the industry. Examples of standard protocols include, for example, HTTP, IIOP, RMI, SMTP, SSL, SHTTP and the like.
  • Examples of a network 112 include wired or wireless solutions such as Ethernet, fiber optic, or the like. However, it should be appreciated that any present or future developed networks and/or network protocols which perform the tasks required for a command and control center to communicate with a threat scanning machine may be used with equal success according to the present invention.
  • the exemplary command and control center 110 communicates with one or more threat scanning machines 106 via the network 112 .
  • the command and control center 110 may transmit data to the threat scanning machine, for example, operational software, authorized users and credentials, threat profiles, etc.
  • the operational software may comprise any combination of software for the operation of the scanning system and/or software for the operation of the management system 100 .
  • the authorized users and credentials which may include, for example, a list of user login names and passwords.
  • Threat profiles may include data that the threat scanning machine uses to aid in identification of threats, for example the shape of potential threat items, and/or the physical properties of an item that may indicate a potential threat.
  • the data transmitted from the command and control center 110 to the threat scanning machine 106 may be any data required for the management and operation of the threat scanning machine and could be used with equal effectiveness according to the present invention.
  • the exemplary threat scanning machine 106 communicates with the command and control center 110 .
  • the threat scanning machine my receive data from the command an control center 110 and/or may transmit data to the command and control center 110 .
  • the data that the threat scanning machine may transmit to the command and control center 110 may include, for example, performance data, requests for operator assistance, threat detection data, and/or the like.
  • the exemplary command and control center 110 may communicate with one or more command and control centers 104 and/or 102 .
  • the command and control centers 110 are interconnected to command and control centers 104 .
  • the command and control centers 104 are interconnected to command and control center 102 .
  • control centers are arranged in a hierarchical manner to provide for the centralized management of many threat scanning machines 106 from a central command and control center 102 , thus providing more efficient management of the threat scanning machines 106 .
  • FIG. 2 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system.
  • a command and control center 104 at one level is interconnected with a command and control center 110 of another level.
  • the command and control center 104 comprises, in addition to standard control center components, a threat management module 206 , a remote management module 208 and a maintenance server module 210 .
  • the exemplary command and control center 110 comprises, in addition to standard control center components, a threat management module 222 , a remote management module 224 and a maintenance server module 226 .
  • the exemplary command and control center 110 is interconnected to one or more exemplary threat scanning machines 106 .
  • the exemplary threat scanning machines 106 comprise, in addition to standard threat scanning machine components, a threat scanning machine computer 202 and a scanning system 204 .
  • the exemplary threat scanning machine computer 202 comprises, in addition to standard computer hardware and software components, a management system interface module 220 and a scanning system interface module 218 .
  • the management system interface module 220 comprises a threat management module 212 , a remote management module 214 , and a maintenance server module 216 .
  • the exemplary threat management module 212 , remote management module 214 , and maintenance server module 216 are adapted to provide the interface and logic necessary for the threat scanning machine 106 to be connected to the maintenance and control system; these modules also communicate with the scanning system interface module 218 .
  • the threat scanning machine computer 202 may be a standard PC.
  • the threat scanning machine computer 202 may be a specialized computer adapted specifically to control the threat scanning machine 106 .
  • the threat scanning machine management system 100 may be designed to adapt to any existing threat scanning machine computer 202 in order to allow the threat scanning machine 106 to connect and communicate within the threat scanning machine management system.
  • system interface module 220 can be housed in a computer separate from the threat scanning machine computer 202 ; this construction may be useful in situations where the execution of the system interface module 220 may present too great a processing and/or communications burden for the threat scanning machine computer 202 .
  • the exemplary threat management module 206 of the command and control center 104 communicates with the threat management module 222 of the command and control center 110 .
  • the threat management module 222 of the command and control center 110 communicates with the threat management module 212 of the threat scanning machine 106 .
  • the threat management information comprises any information related to the management of threats. Examples of such information include Threat Image Projections (TIP), which are non-threat images with threats inserted into them for testing purposes, threats detected within a particular piece of baggage, or messages alerting the threat scanning machine operators to specific or general types of security risks that may be present or that may be attempted.
  • TIP Threat Image Projections
  • the exemplary remote management module 208 of the command and control center 104 communicates with the remote management module 224 of the command and control center 110 .
  • the remote management module 224 of the command and control center 110 communicates with the remote management module 214 of the threat scanning machine 106 .
  • the exemplary maintenance server module 210 of the command and control center 104 communicates with the maintenance server module 226 of the command and control center 110 .
  • the maintenance server module 226 of the command and control center 110 communicates with the maintenance server module 216 of the threat scanning machine 106 .
  • the command and control center 110 and the threat scanning machine 106 may communicate with each other using a predefined interface format.
  • a predefined format allows for the command and control center 110 to be connected to any threat scanning machine 106 that has been adapted to work in accordance with the present invention.
  • the tables below provide an example of a predefined interface between the command and control center 110 and the threat scanning machine 106 . However, it should be appreciated that these tables merely represent an exemplary interface for illustration purposes. An actual interface may vary in both content and design, while still be used with equal success, depending on contemplated uses of the invention.
  • TABLE 1 Interface Message Operator Bag Information Screener Bag Information Threat Information Alarm Information TIP Truth Information Event Information User Keystroke Information TIP Configuration Threat Detection Configuration
  • Table 1 shows the messages of an exemplary interface between the command and control center 110 and the threat scanning machine 106 .
  • the threat scanning machine 106 transmits messages to the command and control center 110 , including, for example, Operator Bag Information, Screener Bag Information, Threat Information, Alarm Information, Threat Image Projection (TIP) Truth Information, Event Information, and/or User Keystroke Information.
  • TIP Threat Image Projection
  • Event Information Event Information
  • User Keystroke Information While the command and control enter 110 transmits the TIP Configuration and Threat Detection Configuration messages to the threat scanning machine 106 .
  • Table 2 shows the contents of an exemplary Operator Bag Information message.
  • the Operator Bag Information message provides the command and control center 110 with information relating to a particular piece of baggage that has been scanned by the threat scanning machine 106 .
  • the Operator Bag Information message is used to transmit information gathered by an operator on a particular bag.
  • a supervisor or screener can review the Operator Bag Information message in assisting the operator in assessing a potential threat.
  • Another use of the Operator Bag Information message may be to monitor the performance of an operator by placing a test bag containing a known threat or threat-like object in order to evaluate the operator's performance in identifying and assessing the potential threat.
  • a further use of the Operator Bag Information; message is to collect the messages over time in order to form statistical models of the operator bag information. These statistical models may then be used to further enhance the operation of the threat scanning machine management system.
  • Table 3 shows the contents of an exemplary Screener Bag Information message.
  • the Screener Bag Information message provides the command and control center 110 with information from a particular screener about a particular piece of baggage.
  • a screener may be called upon to search the bag physically.
  • the Screener Bag Information message is used to transmit information gathered by a Screener on a particular bag, such as the results of the physical search, threats found or not found, and any action taken by security with regard to the passenger or the baggage.
  • a supervisor can review the Screener Bag Information in assisting the screener and operator in assessing and dealing with a potential threat.
  • Another use of the Screener Bag Information message may be to monitor the performance of a screener by placing a test bag containing a known threat or threat-like object in order to evaluate the screener's performance in identifying and assessing the potential threat.
  • a further use of the Screener Bag Information message is to collect the messages over time and correlate them with other system data, such as operator bag messages, in order to form statistical models of the screener bag information. These statistical models may then be used to further enhance the operation of the threat scanning machine management system.
  • An important aspect of the present invention achieved through the operator and screener bag information messages, is that baggage may be tracked and associated with a particular person as that person moves about from place to place. For example, the information about a particular person's bag may be gathered as the person travels from location to location. The threat scanning can then be augmented with historical bag information data in order to further inform the operator, screener, or supervisor of the need for further inspection of the bag. Additionally, the baggage may be associated with an owner or carrier and vice versa, thereby permitting the threat scanning machine management system to enhance the threat scanning with auxiliary information about the owner or carrier to further enhance the security.
  • Table 4 above shows the contents of an exemplary Threat Information message.
  • the Threat Information message provides the command and control center 110 with information about a particular threat detected by the threat scanning machine 106 .
  • Threat Information messages may be transferred to the command and control center for assistance in assessment by a supervisor. Additionally the supervisor in the command and control center may pass the message along to a more senior supervisor at a regional or national level command and control center. Further still, the system can be configured to automatically forward messages to higher levels in the hierarchy based on preselected or dynamic criteria, such as threat type or threat category. In this manner a threat that once was only able to be viewed and assessed on site, may now be able to be assessed by numerous people with possibly increasing levels of expertise, thereby by making efficient use of the supervisor's time through a hierarchical system of review and assessment of potential threats. This process can be carried out in a very expeditious manner through the interconnection of the threat scanning machine and the command and control centers on a distributed network.
  • a further use of the Threat Information message is for the threat management system as a whole to scan for incidents of like or similar threats and alert supervisors and threat scanning machine operators to patterns in the data which may indicate a security breach is being attempted.
  • Still another use of the Threat Information message is to gather information on things that have been identified as threats, but in actuality are only items of interest for purposes other than security.
  • the threat scanning machine could possibly be configured to monitor for aerosol cans within baggage and record statistics related to their occurrence in the baggage. This type of statistical information on “threats” could be used to guide policies regarding acceptable items, for general research into items in baggage, or for other such purposes.
  • the data may be collected over time and used to build statistical models of potential threats and their rates' of occurrence.
  • Table 5 shows the contents of an exemplary Alarm Information message.
  • the Alarm Information message provides the command and control center 110 with information about a particular alarm from the threat scanning machine 106 .
  • the Alarm Information messages provide information useful to achieving management goals.
  • the Alarm Information may be transferred both vertically (i.e. from threat scanning machine to command and control center and on up the chain of command and control centers) and horizontally (i.e. threat scanning machine to threat scanning machine) in order to inform management and other operators of threat events in a real time manner.
  • This real time reporting of threat event information makes an added dimension in security response possible, namely one of recognizing a looming security risk that may be geographically disbursed.
  • Table 6 shows the contents of an exemplary Event Information Message.
  • the Event Information message provides the command and control center 110 with information about a particular event that occurred at a threat scanning machine 106 .
  • the Event Information messages provide information useful to achieving management goals.
  • the Event Information may be transferred both vertically (i.e. from threat scanning machine to command and control center and on up the chain of command and control centers) and horizontally (i.e. threat scanning machine to threat scanning machine) in order to inform management and other operators of threat events in a real time manner.
  • This real time nature of the reporting of threat event information brings a new dimension in security response, namely one of recognizing a looming security risk that may be geographically distributed.
  • statistical trends may be analyzed to aid management in improving the efficiency and security of the threat scanning machines.
  • Table 7 shows the contents of an exemplary User Keystroke Information Message.
  • the User Keystroke Information Message provides the command and control center 110 with details from the threat scanning machine 106 regarding the keystrokes of a user in the processing of a particular piece of baggage.
  • the User Keystroke Information message can be used for several management and supervisory purposes.
  • the keystroke information may be used as a training aid by permitting supervisor to oversee the keystrokes used by a scanning machine operator and determine if the operator has used the scanning effectively, or if further training is needed in a particular area. Further, the keystroke information may be collected over time to study the efficiency of the threat scanning machine operators. Further still, the keystroke information may provide additional details to a supervisor who is assisting a scanning machine operator with a possible threat presence. Yet another use of the keystroke information may be to correlate the keystroke information with the image data and recreate, or playback, what took place at a particular machine to look for suspicious activity by the operator or as an aid in analyzing machine performance and debugging the threat scanning machine software.
  • An important aspect of the threat scanning machine management system is that is a system for managing both the threat scanning machine equipment and the personnel operating the threat scanning machines.
  • FIG. 3 is a functional block diagram of an exemplary threat scanning machine 106 .
  • the threat scanning machine 106 comprises, in addition to the standard threat scanning machine components, a computer 202 and a scanning system 204 .
  • the computer 202 comprises, in addition to standard computer components, management system interface module 220 and a scanning system interface module 218 .
  • the management system interface module 220 comprises a threat management module 212 , a remote management module 214 , and a maintenance server module 216 .
  • the scanning system interface module 218 comprises one or more interface modules 320 , and, optionally, a low level driver module 334 .
  • the threat management module 212 comprises a parent connection logic module 302 , an action logic module 304 , and an Application Programming Interface (API) logic module 306 .
  • the remote management module 214 comprises a parent connection logic module 308 , an action logic module 310 and an API logic module 312 .
  • the maintenance server module 216 comprises a parent connection logic module 314 , an action logic module 316 , and an API logic module 318 .
  • the threat scanning machine computer 202 executes the management system interface module 220 and the threat scanning machine physical machine interface software 218 .
  • the exemplary interface and control logic module 302 contains the logic necessary for the connection and communication with the threat management module within the control computer.
  • the Operation Logic component 304 contains operational logic.
  • the application programming interface (API) component 306 contains the logic necessary for interfacing with the scanning system interface module 218 .
  • the remote management module 214 contains interface and control logic module 308 that contains the logic necessary for the connection and communication with the remote management module in a command and control center.
  • the operational logic module 310 that contains operational logic and an application programming interface (API) component 312 that contains the logic necessary for interfacing with the scanning system interface module 218 .
  • API application programming interface
  • the interface and control logic module 314 contains the logic necessary for the connection and communication with the maintenance server module in the command and control center. Also within the threat scanning machine maintenance server module 216 is an operational logic module 316 that contains operational action logic and an application programming interface (API) component 318 that contains the logic necessary for interfacing with the scanning system interface module 218 .
  • API application programming interface
  • the scanning system interface module 218 may contain one or more modules 320 .
  • These modules 320 may provide interface logic necessary for the management system interface module 220 to be interconnected with and/or to control the scanning system 204 .
  • the modules 320 may, for example, provide user interface functionality to the threat scanning machine 106 operator.
  • the operator interface module 320 may reside within the management system interface module 220 . Examples of interface modules 320 include weapons processing, explosive processing, data archiving, diagnostics, image capture, material movement system, and/or the like.
  • the scanning system interface module 218 also may contain a low-level driver module 334 adapted to directly control the circuitry, software, and/or mechanics of the scanning system 204 .
  • a low-level driver module 334 adapted to directly control the circuitry, software, and/or mechanics of the scanning system 204 .
  • the threat scanning machine 106 shown in FIG. 3 is an exemplary embodiment shown for illustration purposes, and any threat scanning machine can be utilized within the threat scanning machine management system 100 with equal success.
  • the exact software component configuration of a particular threat scanning machine 106 will depend on its contemplated use and the capabilities of its subsystems, in accordance with the present invention.
  • FIG. 4 is a functional block diagram of an exemplary embodiment of the control center computer side of an exemplary threat scanning machine management system 100 .
  • the command and control center software 402 comprises, in addition to standard control center software components, a threat management module 404 , a remote management module 406 , and a maintenance server module 408 .
  • the threat management module 404 comprises a parent connection logic module 410 , a report logic module 412 , an instruction logic module 414 , and a threat scanning machine receive and control logic module 416 .
  • the remote management module 406 comprises a parent connection logic module 418 , a report logic module 420 , an instruction logic module 422 , and a threat scanning machine receive and control logic module 424 .
  • the maintenance server module 408 comprises a parent connection logic module 426 , a report logic module 428 , an instruction logic module 430 , and a threat scanning machine receive and control logic module 432 .
  • the parent connection logic modules ( 302 , 308 , and 314 ) of the threat scanning machine 106 may be similar to the parent connection logic modules ( 410 , 418 , and 426 ) of the command and control center 110 .
  • FIG. 5 is a functional block diagram of an exemplary embodiment of a threat management module in accordance with the present invention.
  • a command and control center threat management module 404 is shown connected to a threat scanning machine threat management module 212 .
  • the command and control center threat management module 404 comprises an interface and control logic module 410 , a configuration updater 502 , a configuration database 504 , a report generator and viewer module 506 , one or more reports 508 , an instruction logic module 414 , a data management logic module 412 , threat management database 510 and interface and control logic module 416
  • the threat scanning machine threat management module 212 comprises an interface and control logic module 302 , an instruction logic module 304 , a data management logic module 512 , a threat management database 514 , an API interface logic module 306 , and a scanning system interface module 218 .
  • FIG. 6 is a functional block diagram of an exemplary embodiment of a remote management module in accordance with the present invention.
  • a command and control center remote management module 406 is shown connected to a threat scanning machine remote management module 214 .
  • the command and control center remote management module 406 comprises an interface and control logic module 418 , a configuration updater 602 , a configuration database 604 , a scheduler 606 , a system administration updater 610 , one or more reports 608 , an instruction logic module 422 , a data management logic module 420 , remote management database 612 and interface and control logic module 424 .
  • the threat scanning machine remote management module 214 comprises an interface and control logic module 308 , an instruction logic module 310 , a data management logic module 614 , a remote management database 616 , an API interface logic module 312 , and a scanning system interface module 218 .
  • FIG. 7 is a functional block diagram of an exemplary embodiment of a maintenance server module in accordance with the present invention.
  • a command and control center maintenance server module 408 is shown connected to a threat scanning machine maintenance server module 216 .
  • the command and control center maintenance server module 408 comprises an interface and control logic module 426 , a configuration updater 702 , a configuration database 704 , a configuration management viewer 710 , a data input interface 708 , one or more data files 706 , an instruction logic module 430 , a data management logic module 428 , maintenance server and configuration database 712 , a scheduler module 714 and an interface and control logic module 432 .
  • the threat scanning machine threat management module 216 comprises an interface and control logic module 314 , an instruction logic module 316 , a data management logic module 716 , a maintenance server database 718 , an API interface logic module 318 and a scanning system interface module 218 .
  • FIG. 8 is a functional block diagram of an exemplary embodiment of a control center database and web service connections in accordance with the present invention.
  • the maintenance and control system data store 802 comprises a database access logic module 804 , a web server logic module 806 and a database 808 .
  • the data management logic modules 412 , 420 , and 428 of the threat management, remote management, and maintenance server modules, respectively, are connected to the database access logic module 804 .
  • the report generator and viewer 506 and the configuration updater 502 of the threat management module 404 are connected to the web server logic module 806 .
  • the system administration updater 610 , the scheduler 606 and the configuration updater 602 of the remote management module 406 are connected to the web server logic module 806 .
  • the configuration management viewer 710 , the scheduler 714 , the data input interface 708 and the configuration updater 702 of the maintenance server 408 are connected to web server logic module 806 .
  • the web server logic module 806 is connected to the database 8
  • the data management logic modules 412 , 420 , and 428 of the threat management, remote management, and maintenance server modules respectively communicate with the database access logic module 804 .
  • the database access logic module provides the interface connectivity to the database 808 .
  • the web server logic module 806 provides the command and control center with web service access to the database 808 .
  • FIG. 9 is a functional block diagram of an exemplary control and maintenance system showing a web browser connection in accordance with the present invention.
  • web browsers 902 and 904 are shown connected to the web server logic module 806 . While two web browsers are shown, it should be appreciated that multiple web browsers may connect to the web server logic module 806 .
  • FIG. 10 is a functional block diagram of an exemplary threat scanning machine architecture.
  • the threat scanning machine comprises a sensor 1002 , a data acquisition system 1004 , a reconstruction computer 1006 , and an operator workstation 1008 .
  • the reconstruction computer 1006 comprises a control logic module 1010 .
  • the operator workstation 1008 presents a graphical user interface to the operator of the threat scanning machine.
  • raw data from the sensor 1002 is collected by the data acquisition system 1004 .
  • the raw data is then transmitted to the reconstruction computer 1006 .
  • the reconstruction computer 1006 processes the raw data and may provide a three-dimensional image or a two-dimensional image to the operator workstation 1008 .
  • the software for the maintenance and control system resides on the operator workstation 1008 .
  • the threat scanning machine management system can download software or data to the reconstruction computer 1006 , operator workstation 1008 , and/or other components of the threat scanning machine that may require software or data to operate.
  • FIG. 11 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing an exemplary approach to network security for two different levels of security, confidential and secret.
  • the public network 1102 for example a wide area network (WAN) is connected to both a confidential communications system 1104 and a secret communications system 1106 .
  • the confidential communications system comprises a router 1112 , a triple data encryption standard (3DES) virtual private network connection 1114 , a firewall 1116 and a local area network (LAN) switch 1118 .
  • An exemplary private network 1108 is connected to the LAN switch 1118 .
  • the secret communications system 1106 comprises a router 1120 , a National Security Agency (NSA) cryptographic processor 1122 , a firewall 1124 , and a LAN switch 1126 .
  • a private network 1110 is connected to the LAN switch 1126 .
  • NSA National Security Agency
  • FIG. 12 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary security components in accordance with the present invention.
  • a threat scanning machine 106 is connected to the public wide area network (WAN) 1102 .
  • a command and control center 110 is also connected to the public WAN 1102 .
  • Unauthorized users 1202 may be connected to the public wide area network.
  • the threat scanning machine communications system comprises a router/phone 1112 , an encryption module 1114 or 1120 depending on the level of security, a firewall 1116 , and a local area network (LAN) switch 1118 .
  • LAN local area network
  • the command and control center 110 comprises a threat management computer 404 , a remote management computer 406 , a maintenance server computer 408 , a web server logic module 806 , log files 1204 , a database 808 , a router/phone 1112 , an encryption device 1114 or 1120 depending on the level of security required, a firewall 1116 and a LAN switch 1118 .
  • the unauthorized users 1202 are restricted from accessing the threat scanning machine 106 or the command and control center 110 . While the encryption devices 1114 or 1120 , permit the threat scanning machine 106 and the command and control center 110 to communicate in a secure manner.
  • FIG. 13 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary alternative approaches to the network connection of security equipment in accordance with the present invention.
  • FIG. 13 shows two approaches to network security within a transportation facility.
  • the threat scanning machine 106 requires the security hardware and software to be present with the threat scanning machine.
  • FIG. 13B there is one set of security hardware and software for an entire facility and the threat scanning machines 106 are all interconnected to the one set of communications security hardware and software.
  • the threat scanning machine comprises application code 220 , a local area network switch 1118 , a firewall 1116 , an encryption device 1114 or 1120 depending on the level of security required, and a router/phone 1112 .
  • the threat scanning machine 106 containing its own set of communications security hardware and software is able to be directly connected to the public wide area network 1120 .
  • the communications security hardware and software may be placed in a central locations and accessed by one or more threat scanning machines 106 .
  • the communications equipment comprises a local area network switch 1118 , a firewall 1116 , an encryption device 1114 or 1120 depending on the level of security required, and a router/phone 1112 .
  • the threat scanning machines 106 each contain their own application code 220 .
  • the threat scanning machine are interconnected to the communications security equipment via the LAN switch 1118 .
  • each threat scanning machine 106 communicates through the LAN switch 1118 to the communications security hardware and software in order to access the public wide area network 1102 .
  • FIG. 14 shows a functional block diagram of a threat scanning machine 106 interconnected with a command and control center 110 .
  • FIG. 14 shows an exemplary message interface between the threat scanning machine 106 and the command and control center 110 in accordance with the messages described in Tables 1 through 7 above.
  • the threat scanning machine 106 provides the following message to the command and control center 110 : operator bag information, the screener bag information, the threat information, alarm information, TIP truth information, event information, and user keystroke information.
  • the command and control center 110 provides the following messages to the threat scanning machine 106 , TIP configuration and threat detection configuration.
  • One way that the personnel using a threat scanning machine management system can interact with the system is through computer adapted to provide a graphical user interface.
  • the following is a description of an exemplary graphical user interface in accordance with the present invention.
  • the graphical user interface shown in the figures is provided for illustrative purposes.
  • a particular embodiment of the invention may have a graphical user interface that is implemented, configured, or adapted differently depending on the contemplated uses of the invention.
  • FIG. 15 is an illustration of an exemplary user interface for the threat scanning machine management system showing the main menu screen.
  • the main menu comprises Remote Management, Threat Management, Maintenance Server, TIP Management, Log Off, and Help choices.
  • a tab style user interface element comprises the tabs choices of Alarms, Events, Dnld (an abbreviation for download), and Comm (an abbreviation for communications).
  • FIG. 16 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the Remote Management menu choice.
  • the Remote Management menu comprises User Administration, Fault Reporting, System Monitoring, and System Administration choices.
  • FIG. 17 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the Threat Management menu choice.
  • the Threat Management menu comprises Reports and Forms menu choices.
  • FIG. 18 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the Maintenance Server menu choice.
  • the Maintenance Server menu comprises File Management, Profile Management, and Download menu choices.
  • FIG. 19 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the TIP Management menu choice.
  • the TIP management menu comprises Image Management, Library Management, and Library Distribution menu choices.
  • the Help menu choice the user will be presented with information on how to operate the threat scanning machine management system.
  • FIG. 20 shows an exemplary Events tab screen.
  • FIG. 26 shows an exemplary Comm (short for communications) tab screen.
  • the tab screens allow the operator to quickly ascertain the status of important system functions.
  • FIG. 21 is an illustration of an exemplary user interface for the threat scanning machine management system showing the User Administration screen.
  • FIG. 22 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Fault Reporting selection dialog interface.
  • FIG. 23 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Performance Information dialog.
  • FIG. 24 is an illustration of an exemplary user interface for the threat scanning machine management system showing the System Administration screen.
  • the Threat Management menu shown in FIG. 17 if the user selects, from the Threat Management menu, the Reports menu choice, the reports selection will be displayed. Examples of the types of reports available include the Download Schedule shown in FIG. 25 , the Throughput Report shown in FIG. 27 , the Personnel Report shown in FIG. 28 , the Current Alarm Report shown in FIG. 29 , the Historical Bag/Threat Information Report shown in FIG. 30 , the Threat Type Information Report shown in FIG. 31 , the Fault Report shown in FIG. 37 and the All Actions Taken Information Report shown in FIG. 32 .
  • FIG. 33 is an illustration of an exemplary user interface for the threat scanning machine management system File Management screen. From the File management screen, the user can add files.
  • FIG. 34 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Profile Management screen. From the Profile Management screen, the user can define a profile comprising one or more files that require downloading. The profile is a way of bundling the files that require downloading together.
  • FIG. 35 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Download Management screen. Using the Download Management screen, the user can schedule a download of a previously defined profile.
  • FIG. 36 is an illustration of an exemplary user interface for the threat scanning machine management system showing the TIP Image Management screen.
  • FIG. 37 shows an exemplary Fault Report screen. There are no faults shown in this example. However, if faults were present for the report criteria specified, such faults would be displayed in the table along with the pertinent fault details.
  • FIG. 38 shows an exemplary threat scanning machine management system user interface that has been adapted to be displayed on a handheld computer, laptop computer, or the like.
  • FIG. 38 is presented to show the main menu screen on a simulated handheld device. While the other screens are not shown on a handheld device is should be appreciated that the entire threat management system user interface may be adapted to use on handheld computer, laptop computer, portable computer, network enabled communications device, or any type of portable computing device.
  • the threat scanning machine management system can be implemented on a general-purpose computer, a special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element, and ASIC or other integrated circuit, a digital signal processor, a hardwired electronic or logic circuit such as a discrete element circuit, a programmed logic device such as a PLD, PLA, FPGA, PAL, or the like.
  • any process capable of implementing the functions described herein can be used to implement a system for the management of threat scanning machines according to this invention.
  • the disclosed system may be readily implemented in software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer platforms.
  • the disclosed system for managing threat scanning machines may be implemented partially or fully in hardware using standard logic circuits or a VLSI design.
  • Other hardware or software can be used to implement the systems in accordance with this invention depending on the speed and/or efficiency requirements of the systems, the particular function, and/or a particular software or hardware system, microprocessor, or microcomputer system being utilized.
  • the threat scanning machine management system illustrated herein can readily be implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the functional description provided herein and with a general basic knowledge of the computer and network communication arts.
  • the disclosed methods may be readily implemented in software executed on programmed general-purpose computer, a special purpose computer, a microprocessor, or the like.
  • the systems and methods of this invention can be implemented as program embedded on personal computer such as JAVA® or CGI script, as a resource residing on a server or graphics workstation, as a routine embedded in a dedicated encoding/decoding system, or the like.
  • the system can also be implemented by physically incorporating the system and method into a software and/or hardware system, such as the hardware and software systems of an image processor.

Abstract

Disclosed is a dynamically configurable threat scanning machine management system that utilizes a network to connect threat scanning machines with a central control computer. The central control computer can transmit, among other things, operational software and threat profiles to the threat scanning machines, while the threat scanning machines can transmit, among other things, images and performance data to the central computer. The threat scanning machine management system can be arranged in a hierarchical manner, which enables threat scanning machines at various locations to be connected into regional, national or international control centers for greater management efficiency. The network may be wireless and the control computer may be portable, enabling a supervisor to remotely manage the threat scanning machines while remaining mobile about the facility, or elsewhere. Additionally, the threat scanning machine management system can be accessed and monitored remotely from a web browser via secure Internet access.

Description

  • The present invention relates generally to system management, and, more particularly, to the management of threat scanning machines.
  • Threat scanning machines are often employed in locations where safety and security are at issue. Transportation facilities, for example, airports, train stations, seaports, and the like, may employ threat scanning machines to detect security threats within passenger or freight baggage. Other facilities, such as office buildings, government buildings, court houses, museums and the like may employ threat scanning machines to detect restricted items being carried by a person seeking entry to the facility. A threat scanning machine, as used herein, refers to any device capable of detecting an object defined as a threat. A threat, as used herein, can be anything that is restricted from being brought aboard a vehicle, into a building or into an area.
  • Threat scanning machines may be of different make and model, including carry-on bag scanning machines, checked-bag scanning machines, walk-through metal detectors, x-rays, computerized tomography devices, magnetic resonance imaging devices, and the like, thus requiring individualized maintenance and control of each machine's software and data components. The task of individually maintaining and controlling each machine may be time consuming, prone to error and expensive. For example, when supervisor attention is required at a particular machine, the supervisor must physically go to the machine, assess the situation and provide guidance to the threat scanning machine operator. As another example, when the software in an existing threat scanning machine needs to be upgraded, the media containing the upgrade may be required to be carried from machine to machine in order to perform the upgrade. The diversity of threat scanning machine types and the varied locations of threat scanning machines pose obstacles to the efficient management of the threat scanning machines.
  • In an exemplary embodiment of the threat scanning machine management system, the threat scanning machines are connected to a communication network. One or more control center computers are connected to the communication network. The threat scanning machines, possibly of different make and model, are adapted with hardware and software to allow them to communicate over the network with the control center computer. The control center computer is adapted with software and/or hardware to control and manage threat scanning machines. In another exemplary embodiment of the present invention, t-he control computer can transmit data, such as, for example, operational software and threat profiles to the threat scanning machine; and the threat scanning machines may transmit data, such as, for example, images and performance data to the control computer.
  • In yet another exemplary embodiment of the present invention, a supervisor may view the images or performance data of a threat scanning machine remotely on the control center computer, assess the situation and assist the threat scanning machine operator remotely, thereby permitting the supervisor to manage multiple threat scanning machines in an efficient manner. In still another exemplary embodiment of the present invention, the threat scanning machine management system may be dynamically configurable, the network may be a wireless network, and the control center computer may be a portable device, thus permitting a superior to manage the threat scanning machines while remaining mobile.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system;
  • FIG. 2 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system showing the control centers connected to a threat scanning machine in accordance with the present invention;
  • FIG. 3 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system showing the details of an exemplary threat scanning machine in accordance with the present invention;
  • FIG. 4 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system showing the details of an exemplary control center in accordance with the present invention;
  • FIG. 5 is a functional block diagram of an exemplary embodiment of the logical functions of an exemplary threat management module in accordance with the present invention;
  • FIG. 6 is a functional block diagram of an exemplary embodiment of a remote management module in accordance with the present invention;
  • FIG. 7 is a functional block diagram of an exemplary embodiment of a maintenance server module in accordance with the present invention;
  • FIG. 8 is a functional block diagram of an exemplary embodiment of a control center database and web service connections in accordance with the present invention;
  • FIG. 9 is a functional block diagram of an exemplary control and maintenance system showing a web browser connection in accordance with the present invention;
  • FIG. 10 is a functional block diagram of an exemplary threat scanning machine architecture in accordance with the present invention;
  • FIG. 11 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing an exemplary approach to network security in accordance with the present invention;
  • FIG. 12 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary security components in accordance with the present invention;
  • FIGS. 13A and 13B are a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary alternative approaches to the network connection of security equipment in accordance with the present invention;
  • FIG. 14 is a functional block diagram of an exemplary message interface between a threat scanning machine and the threat scanning machine management system in accordance with the present invention;
  • FIG. 15 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the main menu screen;
  • FIG. 16 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Remote Management menu;
  • FIG. 17 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Threat Management menu;
  • FIG. 18 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Maintenance Server menu;
  • FIG. 19 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the items of the Threat Image Projection (TIP) Management menu;
  • FIG. 20 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing Event information;
  • FIG. 21 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing User Administration data;
  • FIG. 22 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Fault Reporting selection dialog;
  • FIG. 23 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Report Filter selection dialog;
  • FIG. 24 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing System Administration data;
  • FIG. 25 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a download schedule;
  • FIG. 26 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing the System Administration screen;
  • FIG. 27 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Throughput Report;
  • FIG. 28 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Personnel Report;
  • FIG. 29 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Current Alarm Report;
  • FIG. 30 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing an Historical Bag/Threat Information Report;
  • FIG. 31 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Threat Type Information Report;
  • FIG. 32 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing an All Actions Taken Information Report;
  • FIG. 33 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a File Management Report;
  • FIG. 34 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Profile Management Report;
  • FIG. 35 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Download Management Report;
  • FIG. 36 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a TIP Image Management Report;
  • FIG. 37 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface showing a Fault Report; and
  • FIG. 38 is an illustration of an exemplary embodiment of the threat scanning machine management system user interface adapted for use on a handheld or portable computer showing the main menu screen.
  • DETAILED DESCRIPTION
  • While the exemplary embodiments illustrated herein may show the various components of the threat scanning machine, and corresponding command and control center, collocated, it is to be appreciated that the various components of the system can be located at distant portions of a distributed network, such as a telecommunications network and/or the Internet or within a dedicated communications network. Thus, it should be appreciated that the components of the threat scanning machine and the command and control center, respectively, can be combined into one or more devices or collocated on a particular note of a distributed network, such as a telecommunications network. As will be appreciated from the following description, and for reasons of computational efficiency, the components of the communications network can be arranged at any location within the distributed network without affecting the operation of the system. Also, the exemplary embodiments shown provide a layout of the system in which the subsystems (i.e. Threat Management, Remote Management, and Maintenance Server) are shown separately for conceptual clarity and for illustrative purposes in both the threat scanning machines and the command and control center. However, it should be appreciated, that other layouts, groupings, and/or arrangements of the subsystems within the system can be used.
  • Furthermore, it should be appreciated that the various links connecting the elements can be wired or wireless links, or a combination thereof, or any known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements.
  • FIG. 1 shows a functional block diagram of an exemplary embodiment of a threat scanning machine management system 100. In particular, a command and control center 102 forms a top level of a system hierarchy and is interconnected by a network 112 to a next level comprising command and control centers 104. A command and control center 104 is interconnected with a threat scanning machine 106 by the network 112. A command and control center 104 is interconnected to command and control center 108 and to command and control center 110 via the network 112. A command and control center 110 is interconnected to one or more threat scanning machines 106 via the network 112.
  • The threat scanning machine management system 100 shown in FIG. 1 represents, for purposes of illustration, an exemplary configuration of command and control centers connected to each other and to threat scanning machines. However, it should be appreciated that the system 100 can be configured in order to be adaptable to various contemplated uses of the present invention. The configuration of the system 100 may be static or dynamic depending on contemplated uses of the invention. In an exemplary embodiment, a transportation facility may have an existing network (not shown), and in such a case, the threat scanning machine management system 100 may be adapted to the existing network. Alternatively, in another exemplary embodiment, if an existing network within a transportation facility is insufficient to be able to adapted to meet the communications requirements of the threat scanning machine management system 100 for any reason, such as low bandwidth or poor security, for example, then a new network can be installed for the threat scanning machine management system 100 to communicate over. However, it should be appreciated that any communications medium that allows the threat scanning machines and the control centers to communicate may be used with equal success. In an exemplary embodiment of the invention, the command and control centers and the threat scanning machines communicate over the network 112 using standard protocols common in the industry. Examples of standard protocols include, for example, HTTP, IIOP, RMI, SMTP, SSL, SHTTP and the like. Examples of a network 112 include wired or wireless solutions such as Ethernet, fiber optic, or the like. However, it should be appreciated that any present or future developed networks and/or network protocols which perform the tasks required for a command and control center to communicate with a threat scanning machine may be used with equal success according to the present invention.
  • In operation, the exemplary command and control center 110 communicates with one or more threat scanning machines 106 via the network 112. The command and control center 110 may transmit data to the threat scanning machine, for example, operational software, authorized users and credentials, threat profiles, etc. The operational software may comprise any combination of software for the operation of the scanning system and/or software for the operation of the management system 100. The authorized users and credentials, which may include, for example, a list of user login names and passwords. Threat profiles may include data that the threat scanning machine uses to aid in identification of threats, for example the shape of potential threat items, and/or the physical properties of an item that may indicate a potential threat. However, it should be appreciated that the data transmitted from the command and control center 110 to the threat scanning machine 106 may be any data required for the management and operation of the threat scanning machine and could be used with equal effectiveness according to the present invention.
  • The exemplary threat scanning machine 106 communicates with the command and control center 110. The threat scanning machine my receive data from the command an control center 110 and/or may transmit data to the command and control center 110. The data that the threat scanning machine may transmit to the command and control center 110 may include, for example, performance data, requests for operator assistance, threat detection data, and/or the like.
  • The exemplary command and control center 110 may communicate with one or more command and control centers 104 and/or 102. In the exemplary embodiment shown in FIG. 1, the command and control centers 110 are interconnected to command and control centers 104. The command and control centers 104 are interconnected to command and control center 102. In this exemplary embodiment and configuration of the present invention control centers are arranged in a hierarchical manner to provide for the centralized management of many threat scanning machines 106 from a central command and control center 102, thus providing more efficient management of the threat scanning machines 106.
  • FIG. 2 is a functional block diagram of an exemplary embodiment of a threat scanning machine management system. In particular, a command and control center 104 at one level is interconnected with a command and control center 110 of another level. The command and control center 104 comprises, in addition to standard control center components, a threat management module 206, a remote management module 208 and a maintenance server module 210. The exemplary command and control center 110 comprises, in addition to standard control center components, a threat management module 222, a remote management module 224 and a maintenance server module 226. The exemplary command and control center 110 is interconnected to one or more exemplary threat scanning machines 106. The exemplary threat scanning machines 106 comprise, in addition to standard threat scanning machine components, a threat scanning machine computer 202 and a scanning system 204.
  • The exemplary threat scanning machine computer 202 comprises, in addition to standard computer hardware and software components, a management system interface module 220 and a scanning system interface module 218. The management system interface module 220 comprises a threat management module 212, a remote management module 214, and a maintenance server module 216. The exemplary threat management module 212, remote management module 214, and maintenance server module 216 are adapted to provide the interface and logic necessary for the threat scanning machine 106 to be connected to the maintenance and control system; these modules also communicate with the scanning system interface module 218. In an exemplary embodiment, the threat scanning machine computer 202 may be a standard PC. In another exemplary embodiment, the threat scanning machine computer 202 may be a specialized computer adapted specifically to control the threat scanning machine 106.
  • In yet another exemplary embodiment of the present invention, the threat scanning machine management system 100 may be designed to adapt to any existing threat scanning machine computer 202 in order to allow the threat scanning machine 106 to connect and communicate within the threat scanning machine management system.
  • In still another exemplary embodiment of the present invention, the system interface module 220 can be housed in a computer separate from the threat scanning machine computer 202; this construction may be useful in situations where the execution of the system interface module 220 may present too great a processing and/or communications burden for the threat scanning machine computer 202.
  • In operation, the exemplary threat management module 206 of the command and control center 104 communicates with the threat management module 222 of the command and control center 110. The threat management module 222 of the command and control center 110 communicates with the threat management module 212 of the threat scanning machine 106. The threat management information comprises any information related to the management of threats. Examples of such information include Threat Image Projections (TIP), which are non-threat images with threats inserted into them for testing purposes, threats detected within a particular piece of baggage, or messages alerting the threat scanning machine operators to specific or general types of security risks that may be present or that may be attempted.
  • The exemplary remote management module 208 of the command and control center 104 communicates with the remote management module 224 of the command and control center 110. The remote management module 224 of the command and control center 110 communicates with the remote management module 214 of the threat scanning machine 106.
  • The exemplary maintenance server module 210 of the command and control center 104 communicates with the maintenance server module 226 of the command and control center 110. The maintenance server module 226 of the command and control center 110 communicates with the maintenance server module 216 of the threat scanning machine 106.
  • The command and control center 110 and the threat scanning machine 106 may communicate with each other using a predefined interface format. A predefined format allows for the command and control center 110 to be connected to any threat scanning machine 106 that has been adapted to work in accordance with the present invention. The tables below provide an example of a predefined interface between the command and control center 110 and the threat scanning machine 106. However, it should be appreciated that these tables merely represent an exemplary interface for illustration purposes. An actual interface may vary in both content and design, while still be used with equal success, depending on contemplated uses of the invention.
    TABLE 1
    Interface Message
    Operator Bag Information
    Screener Bag Information
    Threat Information
    Alarm Information
    TIP Truth Information
    Event Information
    User Keystroke Information
    TIP Configuration
    Threat Detection Configuration
  • Table 1 shows the messages of an exemplary interface between the command and control center 110 and the threat scanning machine 106. In this exemplary interface the threat scanning machine 106 transmits messages to the command and control center 110, including, for example, Operator Bag Information, Screener Bag Information, Threat Information, Alarm Information, Threat Image Projection (TIP) Truth Information, Event Information, and/or User Keystroke Information. While the command and control enter 110 transmits the TIP Configuration and Threat Detection Configuration messages to the threat scanning machine 106.
    TABLE 2
    Operator Bag Information
    Field Name Description
    Machine ID Unique Identifier of Threat Scanning Machine
    Bag ID Identification of the bag
    TIP ID Identification of the TIP image
    Logon ID Operator ID
    Bag Start Date CT Date bag entered CT
    Bag Start Time CT Time bag entered CT
    Bag Start Date QR Date bag entered QR
    Bag Start Time QR Time bag entered QR
    Operator Start Date CT Date operator received the image
    Operator Start Time CT Time operator received the image
    Operator End Date CT Date operator completed the transaction
    Operator End Time CT Time operator completed the transaction
    Bag Size Length and/or weight of bag
    Number of Threats Number of threats detected in this bag
    Number of Keystrokes Number of keystrokes used by operator
    Machine Decision Machine indication of possible threat present
    within bag
    Operator Decision Operator indication of possible threat present
    within bag
    Image ID File name if cannot be derived from Bag ID
  • Table 2 shows the contents of an exemplary Operator Bag Information message. The Operator Bag Information message provides the command and control center 110 with information relating to a particular piece of baggage that has been scanned by the threat scanning machine 106.
  • In operation, the Operator Bag Information message is used to transmit information gathered by an operator on a particular bag. A supervisor or screener can review the Operator Bag Information message in assisting the operator in assessing a potential threat. Another use of the Operator Bag Information message may be to monitor the performance of an operator by placing a test bag containing a known threat or threat-like object in order to evaluate the operator's performance in identifying and assessing the potential threat. A further use of the Operator Bag Information; message is to collect the messages over time in order to form statistical models of the operator bag information. These statistical models may then be used to further enhance the operation of the threat scanning machine management system.
    TABLE 3
    Screener Bag Information
    Field Name Description
    Machine ID Unique Identifier of Threat Scanning Machine
    Bag ID Identification of the bag
    Logon ID Screener ID
    Screener Start Date CT Date screener received the image
    Screener Start Time CT Time screener received the image
    Screener End Date CT Date screener completed the transaction
    Screener End Time CT Time screener completed the transaction
    Number of Keystrokes Number of keystrokes used by screener
    Screener Decision Determination of possible threat within bag
    Screener Annotation Screener's notes
  • Table 3 shows the contents of an exemplary Screener Bag Information message. The Screener Bag Information message provides the command and control center 110 with information from a particular screener about a particular piece of baggage.
  • In operation, when a threat scanning machine and/or operator detect a potential threat, a screener may be called upon to search the bag physically. The Screener Bag Information message is used to transmit information gathered by a Screener on a particular bag, such as the results of the physical search, threats found or not found, and any action taken by security with regard to the passenger or the baggage. A supervisor can review the Screener Bag Information in assisting the screener and operator in assessing and dealing with a potential threat. Another use of the Screener Bag Information message may be to monitor the performance of a screener by placing a test bag containing a known threat or threat-like object in order to evaluate the screener's performance in identifying and assessing the potential threat. A further use of the Screener Bag Information message is to collect the messages over time and correlate them with other system data, such as operator bag messages, in order to form statistical models of the screener bag information. These statistical models may then be used to further enhance the operation of the threat scanning machine management system.
  • An important aspect of the present invention, achieved through the operator and screener bag information messages, is that baggage may be tracked and associated with a particular person as that person moves about from place to place. For example, the information about a particular person's bag may be gathered as the person travels from location to location. The threat scanning can then be augmented with historical bag information data in order to further inform the operator, screener, or supervisor of the need for further inspection of the bag. Additionally, the baggage may be associated with an owner or carrier and vice versa, thereby permitting the threat scanning machine management system to enhance the threat scanning with auxiliary information about the owner or carrier to further enhance the security.
    TABLE 4
    Threat Information
    Field Name Description
    Machine ID Unique Identifier of Threat Scanning Machine
    Bag ID Identification of the bag
    CT Compound Type Detected compound type
    CT Mass Measured mass/density
    CT Confidence Algorithm confidence factor
    QR Compound Type Detected compound type
    QR Mass Detected mass
    Viewed by operator Identifies if operator viewed this particular
    threat
    Operator Action Identifies what action the operator took on a
    given threat
    Machine Decision Machine decision of threat/non-threat
    Threat Category Identifies category of threat (e.g. weapon,
    explosive, etc.)
    Picture File Name The name of the file containing the picture
  • Table 4 above shows the contents of an exemplary Threat Information message. The Threat Information message provides the command and control center 110 with information about a particular threat detected by the threat scanning machine 106.
  • In operation Threat Information messages may be transferred to the command and control center for assistance in assessment by a supervisor. Additionally the supervisor in the command and control center may pass the message along to a more senior supervisor at a regional or national level command and control center. Further still, the system can be configured to automatically forward messages to higher levels in the hierarchy based on preselected or dynamic criteria, such as threat type or threat category. In this manner a threat that once was only able to be viewed and assessed on site, may now be able to be assessed by numerous people with possibly increasing levels of expertise, thereby by making efficient use of the supervisor's time through a hierarchical system of review and assessment of potential threats. This process can be carried out in a very expeditious manner through the interconnection of the threat scanning machine and the command and control centers on a distributed network. A further use of the Threat Information message is for the threat management system as a whole to scan for incidents of like or similar threats and alert supervisors and threat scanning machine operators to patterns in the data which may indicate a security breach is being attempted. Still another use of the Threat Information message is to gather information on things that have been identified as threats, but in actuality are only items of interest for purposes other than security. For example, the threat scanning machine could possibly be configured to monitor for aerosol cans within baggage and record statistics related to their occurrence in the baggage. This type of statistical information on “threats” could be used to guide policies regarding acceptable items, for general research into items in baggage, or for other such purposes. In yet another use of the Threat Information messages, the data may be collected over time and used to build statistical models of potential threats and their rates' of occurrence. These statistical models could be fed back into the threat management system in order to improve the accuracy, security, and management efficiency of the threat scanning machine management system.
    TABLE 5
    Alarm Information
    Field Name Description
    Machine ID Unique Identifier of the Threat Scanning Machine
    Bag ID Identification of the bag
    Alarm Severity Identifies the severity of the alarm (e.g. nail
    clippers may be low, scissors may be medium, and
    gun/knife may be high)
    Threat Category Identifies category of threat (e.g. weapon,
    explosive, etc.)
    Threat Confirmed Annotation indicating if a threat was actually found
  • Table 5 shows the contents of an exemplary Alarm Information message. The Alarm Information message provides the command and control center 110 with information about a particular alarm from the threat scanning machine 106.
  • In operation the Alarm Information messages provide information useful to achieving management goals. As a current situational awareness indication, the Alarm Information may be transferred both vertically (i.e. from threat scanning machine to command and control center and on up the chain of command and control centers) and horizontally (i.e. threat scanning machine to threat scanning machine) in order to inform management and other operators of threat events in a real time manner. This real time reporting of threat event information makes an added dimension in security response possible, namely one of recognizing a looming security risk that may be geographically disbursed. By utilizing threat scanning machine management systems in multiple countries it would even be possible for nations to collectively detect and recognize a global security threat event that was in the early stages of being carried out. By collecting Alarm Information messages over time, statistical trends may be analyzed to aid management in improving the efficiency and security of the threat scanning machines.
    TABLE 6
    Event Information
    Field Name Description
    Machine ID Unique Identifier of the Threat Scanning Machine
    Logon ID User ID
    Event Date CT Date event happened
    Event Time CT Time event happened
    Event Code Code responding to event
    Event Detail Text message about event
  • Table 6 shows the contents of an exemplary Event Information Message. The Event Information message provides the command and control center 110 with information about a particular event that occurred at a threat scanning machine 106.
  • In operation the Event Information messages provide information useful to achieving management goals. As a current situational awareness indication, the Event Information may be transferred both vertically (i.e. from threat scanning machine to command and control center and on up the chain of command and control centers) and horizontally (i.e. threat scanning machine to threat scanning machine) in order to inform management and other operators of threat events in a real time manner. This real time nature of the reporting of threat event information brings a new dimension in security response, namely one of recognizing a looming security risk that may be geographically distributed. By collecting Event Information messages over time, statistical trends may be analyzed to aid management in improving the efficiency and security of the threat scanning machines.
    TABLE 7
    User Keystroke Information
    Field Name Description
    Machine ID Unique Identifier of the Threat Scanning Machine
    Logon ID User ID
    Bag ID Identification of the bag
    Keystroke Count Number of keystrokes
    Keystroke
    1 Keystroke code
    Timestamp
    1 Time keystroke occurred
    Keystroke 2 Keystroke code
    Timestamp
    2 Time keystroke occurred
    . . . . . .
    Keystroke n Keystroke code
    Timestamp n Time keystroke occurred
  • Table 7 shows the contents of an exemplary User Keystroke Information Message. The User Keystroke Information Message provides the command and control center 110 with details from the threat scanning machine 106 regarding the keystrokes of a user in the processing of a particular piece of baggage.
  • In operation, the User Keystroke Information message can be used for several management and supervisory purposes. The keystroke information may be used as a training aid by permitting supervisor to oversee the keystrokes used by a scanning machine operator and determine if the operator has used the scanning effectively, or if further training is needed in a particular area. Further, the keystroke information may be collected over time to study the efficiency of the threat scanning machine operators. Further still, the keystroke information may provide additional details to a supervisor who is assisting a scanning machine operator with a possible threat presence. Yet another use of the keystroke information may be to correlate the keystroke information with the image data and recreate, or playback, what took place at a particular machine to look for suspicious activity by the operator or as an aid in analyzing machine performance and debugging the threat scanning machine software.
  • An important aspect of the threat scanning machine management system is that is a system for managing both the threat scanning machine equipment and the personnel operating the threat scanning machines.
  • FIG. 3 is a functional block diagram of an exemplary threat scanning machine 106. In particular, the threat scanning machine 106 comprises, in addition to the standard threat scanning machine components, a computer 202 and a scanning system 204. The computer 202 comprises, in addition to standard computer components, management system interface module 220 and a scanning system interface module 218. The management system interface module 220 comprises a threat management module 212, a remote management module 214, and a maintenance server module 216. The scanning system interface module 218 comprises one or more interface modules 320, and, optionally, a low level driver module 334. The threat management module 212 comprises a parent connection logic module 302, an action logic module 304, and an Application Programming Interface (API) logic module 306. The remote management module 214 comprises a parent connection logic module 308, an action logic module 310 and an API logic module 312. The maintenance server module 216 comprises a parent connection logic module 314, an action logic module 316, and an API logic module 318.
  • In operation, the threat scanning machine computer 202 executes the management system interface module 220 and the threat scanning machine physical machine interface software 218.
  • The exemplary interface and control logic module 302 contains the logic necessary for the connection and communication with the threat management module within the control computer. The Operation Logic component 304 contains operational logic. The application programming interface (API) component 306 contains the logic necessary for interfacing with the scanning system interface module 218.
  • The remote management module 214 contains interface and control logic module 308 that contains the logic necessary for the connection and communication with the remote management module in a command and control center. The operational logic module 310 that contains operational logic and an application programming interface (API) component 312 that contains the logic necessary for interfacing with the scanning system interface module 218.
  • The interface and control logic module 314 contains the logic necessary for the connection and communication with the maintenance server module in the command and control center. Also within the threat scanning machine maintenance server module 216 is an operational logic module 316 that contains operational action logic and an application programming interface (API) component 318 that contains the logic necessary for interfacing with the scanning system interface module 218.
  • An exemplary embodiment of the scanning system interface module 218 is shown in FIG. 3. In particular, the scanning system interface module 218 may contain one or more modules 320. These modules 320 may provide interface logic necessary for the management system interface module 220 to be interconnected with and/or to control the scanning system 204. The modules 320 may, for example, provide user interface functionality to the threat scanning machine 106 operator. In another exemplary embodiment of the invention, the operator interface module 320 may reside within the management system interface module 220. Examples of interface modules 320 include weapons processing, explosive processing, data archiving, diagnostics, image capture, material movement system, and/or the like. In addition, the scanning system interface module 218 also may contain a low-level driver module 334 adapted to directly control the circuitry, software, and/or mechanics of the scanning system 204. It should be appreciated that the threat scanning machine 106 shown in FIG. 3 is an exemplary embodiment shown for illustration purposes, and any threat scanning machine can be utilized within the threat scanning machine management system 100 with equal success. The exact software component configuration of a particular threat scanning machine 106 will depend on its contemplated use and the capabilities of its subsystems, in accordance with the present invention.
  • FIG. 4 is a functional block diagram of an exemplary embodiment of the control center computer side of an exemplary threat scanning machine management system 100. In particular, the command and control center software 402 comprises, in addition to standard control center software components, a threat management module 404, a remote management module 406, and a maintenance server module 408.
  • The threat management module 404 comprises a parent connection logic module 410, a report logic module 412, an instruction logic module 414, and a threat scanning machine receive and control logic module 416.
  • The remote management module 406 comprises a parent connection logic module 418, a report logic module 420, an instruction logic module 422, and a threat scanning machine receive and control logic module 424.
  • The maintenance server module 408 comprises a parent connection logic module 426, a report logic module 428, an instruction logic module 430, and a threat scanning machine receive and control logic module 432. In an exemplary embodiment, the parent connection logic modules (302, 308, and 314) of the threat scanning machine 106 may be similar to the parent connection logic modules (410, 418, and 426) of the command and control center 110.
  • FIG. 5 is a functional block diagram of an exemplary embodiment of a threat management module in accordance with the present invention. In particular, a command and control center threat management module 404 is shown connected to a threat scanning machine threat management module 212. The command and control center threat management module 404 comprises an interface and control logic module 410, a configuration updater 502, a configuration database 504, a report generator and viewer module 506, one or more reports 508, an instruction logic module 414, a data management logic module 412, threat management database 510 and interface and control logic module 416 The threat scanning machine threat management module 212 comprises an interface and control logic module 302, an instruction logic module 304, a data management logic module 512, a threat management database 514, an API interface logic module 306, and a scanning system interface module 218.
  • FIG. 6 is a functional block diagram of an exemplary embodiment of a remote management module in accordance with the present invention. In particular, a command and control center remote management module 406 is shown connected to a threat scanning machine remote management module 214. The command and control center remote management module 406 comprises an interface and control logic module 418, a configuration updater 602, a configuration database 604, a scheduler 606, a system administration updater 610, one or more reports 608, an instruction logic module 422, a data management logic module 420, remote management database 612 and interface and control logic module 424. The threat scanning machine remote management module 214 comprises an interface and control logic module 308, an instruction logic module 310, a data management logic module 614, a remote management database 616, an API interface logic module 312, and a scanning system interface module 218.
  • FIG. 7 is a functional block diagram of an exemplary embodiment of a maintenance server module in accordance with the present invention. In particular, a command and control center maintenance server module 408 is shown connected to a threat scanning machine maintenance server module 216. The command and control center maintenance server module 408 comprises an interface and control logic module 426, a configuration updater 702, a configuration database 704, a configuration management viewer 710, a data input interface 708, one or more data files 706, an instruction logic module 430, a data management logic module 428, maintenance server and configuration database 712, a scheduler module 714 and an interface and control logic module 432. The threat scanning machine threat management module 216 comprises an interface and control logic module 314, an instruction logic module 316, a data management logic module 716, a maintenance server database 718, an API interface logic module 318 and a scanning system interface module 218.
  • FIG. 8 is a functional block diagram of an exemplary embodiment of a control center database and web service connections in accordance with the present invention. In particular, the maintenance and control system data store 802 comprises a database access logic module 804, a web server logic module 806 and a database 808. The data management logic modules 412, 420, and 428 of the threat management, remote management, and maintenance server modules, respectively, are connected to the database access logic module 804. The report generator and viewer 506 and the configuration updater 502 of the threat management module 404 are connected to the web server logic module 806. The system administration updater 610, the scheduler 606 and the configuration updater 602 of the remote management module 406 are connected to the web server logic module 806. The configuration management viewer 710, the scheduler 714, the data input interface 708 and the configuration updater 702 of the maintenance server 408 are connected to web server logic module 806. The web server logic module 806 is connected to the database 808.
  • In operation, the data management logic modules 412, 420, and 428 of the threat management, remote management, and maintenance server modules respectively communicate with the database access logic module 804. The database access logic module provides the interface connectivity to the database 808. The web server logic module 806 provides the command and control center with web service access to the database 808.
  • FIG. 9 is a functional block diagram of an exemplary control and maintenance system showing a web browser connection in accordance with the present invention. In particular, web browsers 902 and 904 are shown connected to the web server logic module 806. While two web browsers are shown, it should be appreciated that multiple web browsers may connect to the web server logic module 806.
  • FIG. 10 is a functional block diagram of an exemplary threat scanning machine architecture. In particular, the threat scanning machine comprises a sensor 1002, a data acquisition system 1004, a reconstruction computer 1006, and an operator workstation 1008. The reconstruction computer 1006 comprises a control logic module 1010. The operator workstation 1008 presents a graphical user interface to the operator of the threat scanning machine.
  • In operation, raw data from the sensor 1002 is collected by the data acquisition system 1004. The raw data is then transmitted to the reconstruction computer 1006. The reconstruction computer 1006 processes the raw data and may provide a three-dimensional image or a two-dimensional image to the operator workstation 1008. In a threat scanning machine adapted to be used with the maintenance and control system, the software for the maintenance and control system resides on the operator workstation 1008. The threat scanning machine management system can download software or data to the reconstruction computer 1006, operator workstation 1008, and/or other components of the threat scanning machine that may require software or data to operate.
  • FIG. 11 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing an exemplary approach to network security for two different levels of security, confidential and secret. In particular, the public network 1102, for example a wide area network (WAN), is connected to both a confidential communications system 1104 and a secret communications system 1106. The confidential communications system comprises a router 1112, a triple data encryption standard (3DES) virtual private network connection 1114, a firewall 1116 and a local area network (LAN) switch 1118. An exemplary private network 1108 is connected to the LAN switch 1118. The secret communications system 1106 comprises a router 1120, a National Security Agency (NSA) cryptographic processor 1122, a firewall 1124, and a LAN switch 1126. A private network 1110 is connected to the LAN switch 1126.
  • FIG. 12 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary security components in accordance with the present invention. In particular, a threat scanning machine 106 is connected to the public wide area network (WAN) 1102. A command and control center 110 is also connected to the public WAN 1102. Unauthorized users 1202 may be connected to the public wide area network. The threat scanning machine communications system comprises a router/phone 1112, an encryption module 1114 or 1120 depending on the level of security, a firewall 1116, and a local area network (LAN) switch 1118. The command and control center 110 comprises a threat management computer 404, a remote management computer 406, a maintenance server computer 408, a web server logic module 806, log files 1204, a database 808, a router/phone 1112, an encryption device 1114 or 1120 depending on the level of security required, a firewall 1116 and a LAN switch 1118.
  • In operation, the unauthorized users 1202 are restricted from accessing the threat scanning machine 106 or the command and control center 110. While the encryption devices 1114 or 1120, permit the threat scanning machine 106 and the command and control center 110 to communicate in a secure manner.
  • FIG. 13 is a functional block diagram of an exemplary embodiment of the threat scanning machine management system showing exemplary alternative approaches to the network connection of security equipment in accordance with the present invention. In particular, FIG. 13 shows two approaches to network security within a transportation facility. In FIG. 13A, the threat scanning machine 106 requires the security hardware and software to be present with the threat scanning machine. In FIG. 13B, there is one set of security hardware and software for an entire facility and the threat scanning machines 106 are all interconnected to the one set of communications security hardware and software.
  • In FIG. 13A, the threat scanning machine comprises application code 220, a local area network switch 1118, a firewall 1116, an encryption device 1114 or 1120 depending on the level of security required, and a router/phone 1112. In operation the threat scanning machine 106 containing its own set of communications security hardware and software is able to be directly connected to the public wide area network 1120.
  • In FIG. 13B, the communications security hardware and software may be placed in a central locations and accessed by one or more threat scanning machines 106. The communications equipment comprises a local area network switch 1118, a firewall 1116, an encryption device 1114 or 1120 depending on the level of security required, and a router/phone 1112. The threat scanning machines 106 each contain their own application code 220. The threat scanning machine are interconnected to the communications security equipment via the LAN switch 1118.
  • In operation, each threat scanning machine 106 communicates through the LAN switch 1118 to the communications security hardware and software in order to access the public wide area network 1102.
  • FIG. 14 shows a functional block diagram of a threat scanning machine 106 interconnected with a command and control center 110. In particular, FIG. 14 shows an exemplary message interface between the threat scanning machine 106 and the command and control center 110 in accordance with the messages described in Tables 1 through 7 above.
  • In operation, the threat scanning machine 106 provides the following message to the command and control center 110: operator bag information, the screener bag information, the threat information, alarm information, TIP truth information, event information, and user keystroke information. The command and control center 110 provides the following messages to the threat scanning machine 106, TIP configuration and threat detection configuration.
  • One way that the personnel using a threat scanning machine management system can interact with the system is through computer adapted to provide a graphical user interface. The following is a description of an exemplary graphical user interface in accordance with the present invention. However, it should be appreciated that the graphical user interface shown in the figures is provided for illustrative purposes. A particular embodiment of the invention may have a graphical user interface that is implemented, configured, or adapted differently depending on the contemplated uses of the invention.
  • FIG. 15 is an illustration of an exemplary user interface for the threat scanning machine management system showing the main menu screen. In particular, the main menu comprises Remote Management, Threat Management, Maintenance Server, TIP Management, Log Off, and Help choices. There is also shown in FIG. 15 a tab style user interface element comprises the tabs choices of Alarms, Events, Dnld (an abbreviation for download), and Comm (an abbreviation for communications).
  • If the user selects the Remote Management menu choice, the Remote Management menu will be displayed. FIG. 16 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the Remote Management menu choice. In particular, the Remote Management menu comprises User Administration, Fault Reporting, System Monitoring, and System Administration choices.
  • If the user selects, from the main menu, the Threat Management menu choice, the Threat Management Menu will be displayed. FIG. 17 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the Threat Management menu choice. In particular, the Threat Management menu comprises Reports and Forms menu choices.
  • If the user selects, from the main menu, the Maintenance Server menu choice, the Maintenance Server menu will be displayed. FIG. 18 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the Maintenance Server menu choice. In particular, the Maintenance Server menu comprises File Management, Profile Management, and Download menu choices.
  • If the user selects, from the main menu, the TIP Management menu choice, the TIP Management menu will be displayed. FIG. 19 is an illustration of an exemplary user interface for the threat scanning machine management system showing the items available under the TIP Management menu choice. In particular, the TIP management menu comprises Image Management, Library Management, and Library Distribution menu choices.
  • If the user sects, from the main menu, the Log Off menu choice, the user will be logged of the system.
  • If the user selects, from the main menu, the Help menu choice, the user will be presented with information on how to operate the threat scanning machine management system.
  • FIG. 20 shows an exemplary Events tab screen. FIG. 26 shows an exemplary Comm (short for communications) tab screen. The tab screens allow the operator to quickly ascertain the status of important system functions.
  • Returning to the Remote Management menu of FIG. 16, if the user selects the User Administration menu choice, the User Administration screen will be displayed. FIG. 21 is an illustration of an exemplary user interface for the threat scanning machine management system showing the User Administration screen.
  • If the users selects, from the Remote Management menu, the Fault Reporting menu choice, the Fault Reporting dialog will appear. FIG. 22 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Fault Reporting selection dialog interface.
  • If the user selects, from the Remote Management menu, the System Monitoring menu choice, the Performance Information dialog will be displayed. FIG. 23 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Performance Information dialog.
  • If the user selects, from the Remote Management menu, the System Administration menu choice, the System Administration menu will be displayed. FIG. 24 is an illustration of an exemplary user interface for the threat scanning machine management system showing the System Administration screen.
  • Turning now to the Threat Management menu shown in FIG. 17, if the user selects, from the Threat Management menu, the Reports menu choice, the reports selection will be displayed. Examples of the types of reports available include the Download Schedule shown in FIG. 25, the Throughput Report shown in FIG. 27, the Personnel Report shown in FIG. 28, the Current Alarm Report shown in FIG. 29, the Historical Bag/Threat Information Report shown in FIG. 30, the Threat Type Information Report shown in FIG. 31, the Fault Report shown in FIG. 37 and the All Actions Taken Information Report shown in FIG. 32.
  • Turning now to the Maintenance Server menu shown in FIG. 18, if the user selects from the Maintenance Server menu, the File Management menu choice, the File Management screen will be displayed. FIG. 33 is an illustration of an exemplary user interface for the threat scanning machine management system File Management screen. From the File management screen, the user can add files.
  • If the user selects, from the Maintenance Server menu, the Profile Management menu choice, the Profile Management screen will be displayed. FIG. 34 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Profile Management screen. From the Profile Management screen, the user can define a profile comprising one or more files that require downloading. The profile is a way of bundling the files that require downloading together.
  • If the user selects, from the Maintenance Server menu, the Download menu choice, the Download Management screen will be displayed. FIG. 35 is an illustration of an exemplary user interface for the threat scanning machine management system showing the Download Management screen. Using the Download Management screen, the user can schedule a download of a previously defined profile.
  • Turning now to the TIP Management menu shown in FIG. 19, if the user selects the Image Management option, the TIP Image Management screen will be displayed. FIG. 36 is an illustration of an exemplary user interface for the threat scanning machine management system showing the TIP Image Management screen.
  • FIG. 37 shows an exemplary Fault Report screen. There are no faults shown in this example. However, if faults were present for the report criteria specified, such faults would be displayed in the table along with the pertinent fault details.
  • FIG. 38 shows an exemplary threat scanning machine management system user interface that has been adapted to be displayed on a handheld computer, laptop computer, or the like. In particular, FIG. 38 is presented to show the main menu screen on a simulated handheld device. While the other screens are not shown on a handheld device is should be appreciated that the entire threat management system user interface may be adapted to use on handheld computer, laptop computer, portable computer, network enabled communications device, or any type of portable computing device.
  • As shown in the above figures, the threat scanning machine management system can be implemented on a general-purpose computer, a special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element, and ASIC or other integrated circuit, a digital signal processor, a hardwired electronic or logic circuit such as a discrete element circuit, a programmed logic device such as a PLD, PLA, FPGA, PAL, or the like. In general, any process capable of implementing the functions described herein can be used to implement a system for the management of threat scanning machines according to this invention.
  • Furthermore, the disclosed system may be readily implemented in software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer platforms. Alternatively, the disclosed system for managing threat scanning machines may be implemented partially or fully in hardware using standard logic circuits or a VLSI design. Other hardware or software can be used to implement the systems in accordance with this invention depending on the speed and/or efficiency requirements of the systems, the particular function, and/or a particular software or hardware system, microprocessor, or microcomputer system being utilized. The threat scanning machine management system illustrated herein can readily be implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the functional description provided herein and with a general basic knowledge of the computer and network communication arts.
  • Moreover, the disclosed methods may be readily implemented in software executed on programmed general-purpose computer, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this invention can be implemented as program embedded on personal computer such as JAVA® or CGI script, as a resource residing on a server or graphics workstation, as a routine embedded in a dedicated encoding/decoding system, or the like. The system can also be implemented by physically incorporating the system and method into a software and/or hardware system, such as the hardware and software systems of an image processor.
  • It is, therefore, apparent that there is provided in accordance with the present invention, systems and methods for managing threat scanning machines. While this invention has been described in conjunction with a number of embodiments, it is evident that many alternatives, modifications and variations would be or are apparent to those of ordinary skill in the applicable arts. Accordingly, applicants intend to embrace all such alternatives, modifications, equivalents and variations that are within the spirit and scope of this invention.

Claims (7)

1. A dynamically configurable maintenance and control system for threat scanning machines located in an airport, the system comprising:
a threat scanning machine in the airport, adapted to communicate via a network; and
a control computer, adapted to communicate via the network with the threat scanning machine and to dynamically re-configure the system by selecting a threat scanning machine for addition to the system;
wherein said selecting is performed in real time in response to current conditions in the airport.
2-11. (canceled)
12. A method of centrally maintaining and controlling threat scanning machines located in an airport, the method comprising:
connecting a control computer to a communication network;
connecting a threat scanning machine to a communication network;
loading the control computer with software to communicate with threat scanning machines;
initiating communication between control computer and threat scanning machine; and
dynamically re-configuring the network by the control computer selecting a threat scanning machine in real time in response to a condition.
13-16. (canceled)
17. A computer program fixed in a tangible medium, the program comprising:
means for controlling a system of threat scanning machines via a network;
means for dynamically selecting a threat scanning machine for addition to the network in real time in response to a condition; and
means for dynamically restricting access of a threat scanning machine to the network.
18. The program of claim 17, wherein the means for dynamically selecting comprises means for identifying an activity taking place in an area near the selected threat scanning machine.
19. The program of claim 18, wherein the area is a portion of an airport.
US11/493,012 2004-03-19 2006-07-26 Threat scanning machine management system Abandoned US20060255929A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/493,012 US20060255929A1 (en) 2004-03-19 2006-07-26 Threat scanning machine management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/804,088 US7183906B2 (en) 2004-03-19 2004-03-19 Threat scanning machine management system
US11/493,012 US20060255929A1 (en) 2004-03-19 2006-07-26 Threat scanning machine management system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/804,088 Continuation US7183906B2 (en) 2004-03-19 2004-03-19 Threat scanning machine management system

Publications (1)

Publication Number Publication Date
US20060255929A1 true US20060255929A1 (en) 2006-11-16

Family

ID=34985672

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/804,088 Active 2024-09-16 US7183906B2 (en) 2004-03-19 2004-03-19 Threat scanning machine management system
US11/493,012 Abandoned US20060255929A1 (en) 2004-03-19 2006-07-26 Threat scanning machine management system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/804,088 Active 2024-09-16 US7183906B2 (en) 2004-03-19 2004-03-19 Threat scanning machine management system

Country Status (1)

Country Link
US (2) US7183906B2 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7684421B2 (en) 2005-06-09 2010-03-23 Lockheed Martin Corporation Information routing in a distributed environment
US7734102B2 (en) 2005-05-11 2010-06-08 Optosecurity Inc. Method and system for screening cargo containers
US7899232B2 (en) 2006-05-11 2011-03-01 Optosecurity Inc. Method and apparatus for providing threat image projection (TIP) in a luggage screening system, and luggage screening system implementing same
US7991242B2 (en) 2005-05-11 2011-08-02 Optosecurity Inc. Apparatus, method and system for screening receptacles and persons, having image distortion correction functionality
US8494210B2 (en) 2007-03-30 2013-07-23 Optosecurity Inc. User interface for use in security screening providing image enhancement capabilities and apparatus for implementing same
US20140283075A1 (en) * 2013-03-15 2014-09-18 Cyber Engineering Services, Inc. Storage appliance and threat indicator query framework
US9632206B2 (en) 2011-09-07 2017-04-25 Rapiscan Systems, Inc. X-ray inspection system that integrates manifest data with imaging/detection processing
US10302807B2 (en) 2016-02-22 2019-05-28 Rapiscan Systems, Inc. Systems and methods for detecting threats and contraband in cargo

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8451974B2 (en) 2003-04-25 2013-05-28 Rapiscan Systems, Inc. X-ray tomographic inspection system for the identification of specific target items
US8223919B2 (en) 2003-04-25 2012-07-17 Rapiscan Systems, Inc. X-ray tomographic inspection systems for the identification of specific target items
US8837669B2 (en) 2003-04-25 2014-09-16 Rapiscan Systems, Inc. X-ray scanning system
US7949101B2 (en) 2005-12-16 2011-05-24 Rapiscan Systems, Inc. X-ray scanners and X-ray sources therefor
US8243876B2 (en) 2003-04-25 2012-08-14 Rapiscan Systems, Inc. X-ray scanners
GB0525593D0 (en) * 2005-12-16 2006-01-25 Cxr Ltd X-ray tomography inspection systems
US9113839B2 (en) 2003-04-25 2015-08-25 Rapiscon Systems, Inc. X-ray inspection system and method
US7270227B2 (en) * 2003-10-29 2007-09-18 Lockheed Martin Corporation Material handling system and method of use
US7183906B2 (en) * 2004-03-19 2007-02-27 Lockheed Martin Corporation Threat scanning machine management system
US7212113B2 (en) * 2004-05-04 2007-05-01 Lockheed Martin Corporation Passenger and item tracking with system alerts
US20050251398A1 (en) * 2004-05-04 2005-11-10 Lockheed Martin Corporation Threat scanning with pooled operators
US20050251397A1 (en) * 2004-05-04 2005-11-10 Lockheed Martin Corporation Passenger and item tracking with predictive analysis
DE102004043158A1 (en) * 2004-09-03 2006-03-23 Smiths Heimann Gmbh Transportable control station for checking persons and luggage
US20070041613A1 (en) * 2005-05-11 2007-02-22 Luc Perron Database of target objects suitable for use in screening receptacles or people and method and apparatus for generating same
US20060282886A1 (en) * 2005-06-09 2006-12-14 Lockheed Martin Corporation Service oriented security device management network
US20070239408A1 (en) * 2006-03-07 2007-10-11 Manges Joann T Threat matrix analysis system
CA2584683A1 (en) * 2006-04-20 2007-10-20 Optosecurity Inc. Apparatus, method and system for screening receptacles and persons
JP5028022B2 (en) * 2006-04-25 2012-09-19 キヤノン株式会社 Printing apparatus and document printing method
US20080060910A1 (en) * 2006-09-08 2008-03-13 Shawn Younkin Passenger carry-on bagging system for security checkpoints
US20080253653A1 (en) * 2007-04-12 2008-10-16 Todd Gable Systems and methods for improving visibility of scanned images
US20090228980A1 (en) * 2008-03-06 2009-09-10 General Electric Company System and method for detection of anomalous access events
TWI387259B (en) * 2008-08-01 2013-02-21 Kathy T Lin System and method for scenario security of web application programs and program product and computer readable recording medium thereof
US10489720B2 (en) * 2017-05-02 2019-11-26 Secureworks Corp. System and method for vendor agnostic automatic supplementary intelligence propagation
US11538319B2 (en) 2020-09-22 2022-12-27 Kyndryl, Inc. Identifying a distributed threat in a security zone

Citations (95)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3666073A (en) * 1971-02-19 1972-05-30 Mannesmann Geisel Gmbh Airport check-in counter with baggage receiving and handling facility
US3678278A (en) * 1970-01-26 1972-07-18 Le Roy E Peil Apparatus for baggage inspection
US3695462A (en) * 1970-08-28 1972-10-03 Rapistan Inc Baggage handling system
US3735853A (en) * 1972-03-01 1973-05-29 G Lingg System for distributing pieces of load such as baggage, parcels etc.
US4137567A (en) * 1974-10-24 1979-01-30 Grube Hans J System for passenger and luggage processing at commercial airports
US4210811A (en) * 1975-11-03 1980-07-01 Heimann Gmbh Drive for moveable shield in luggage screening apparatus
US4471039A (en) * 1982-11-22 1984-09-11 Eastman Kodak Company Photoconductive elements sensitive to radiation in the infrared region of the spectrum
US4604704A (en) * 1984-09-10 1986-08-05 Doboy Packaging Machinery, Inc. High-speed microprocessor-controlled branch conveyor
US4634849A (en) * 1985-04-02 1987-01-06 Klingen Leonard G Uniquely numbered baggage split tag and system for handling baggage
US5153439A (en) * 1987-05-26 1992-10-06 Science Applications International Corporation Multi-sensor explosive detection system using an articifical neural system
US5182764A (en) * 1991-10-03 1993-01-26 Invision Technologies, Inc. Automatic concealed object detection system having a pre-scan stage
US5490218A (en) * 1990-08-10 1996-02-06 Vivid Technologies, Inc. Device and method for inspection of baggage and other objects
US5600303A (en) * 1993-01-15 1997-02-04 Technology International Incorporated Detection of concealed explosives and contraband
US5600700A (en) * 1995-09-25 1997-02-04 Vivid Technologies, Inc. Detecting explosives or other contraband by employing transmitted and scattered X-rays
US5642393A (en) * 1995-09-26 1997-06-24 Vivid Technologies, Inc. Detecting contraband by employing interactive multiprobe tomography
US5793639A (en) * 1995-10-24 1998-08-11 Toyota Jidosha Kabushiki Kaisha Baggage receiving and handling method in airport, baggage receiving and handling system in airport, and baggage automatic handling apparatus
US5796802A (en) * 1996-08-19 1998-08-18 Analogic Corporation Multiple angle pre-screening tomographic systems and methods
US5802289A (en) * 1992-12-21 1998-09-01 Apple Computer, Inc. Method for propagating preemptive bus initialization on an acyclic directed graph
US5870449A (en) * 1996-05-08 1999-02-09 Vivid Technologies, Inc. Operator console for article inspection systems
US5910973A (en) * 1996-07-22 1999-06-08 American Science And Engineering, Inc. Rapid X-ray inspection system
US5920053A (en) * 1997-01-06 1999-07-06 Debrouse; Cynthia R. Passenger identification and baggage control system
US5949842A (en) * 1997-10-10 1999-09-07 Analogic Corporation Air calibration scan for computed tomography scanner with obstructing objects
US5970113A (en) * 1997-10-10 1999-10-19 Analogic Corporation Computed tomography scanning apparatus and method with temperature compensation for dark current offsets
US5974111A (en) * 1996-09-24 1999-10-26 Vivid Technologies, Inc. Identifying explosives or other contraband by employing transmitted or scattered X-rays
US6014628A (en) * 1997-11-03 2000-01-11 Exigent International, Inc. Method and system for tracking any entity through any set of processes utilizing a temporal projection
US6018562A (en) * 1995-11-13 2000-01-25 The United States Of America As Represented By The Secretary Of The Army Apparatus and method for automatic recognition of concealed objects using multiple energy computed tomography
US6044353A (en) * 1998-03-10 2000-03-28 Pugliese, Iii; Anthony V. Baggage check-in and security system and method
US6088423A (en) * 1998-06-05 2000-07-11 Vivid Technologies, Inc. Multiview x-ray based system for detecting contraband such as in baggage
US6218943B1 (en) * 1998-03-27 2001-04-17 Vivid Technologies, Inc. Contraband detection and article reclaim system
US6222452B1 (en) * 1996-12-16 2001-04-24 Confidence International Ab Electronic identification tag
US6230043B1 (en) * 1998-09-30 2001-05-08 General Electric Company Method and apparatus for capturing and automatically transferring an x-ray image to a remote location
US6256404B1 (en) * 1997-10-10 2001-07-03 Analogic Corporation Computed tomography scanning apparatus and method using adaptive reconstruction window
US6265977B1 (en) * 1998-09-11 2001-07-24 Motorola, Inc. Radio frequency identification tag apparatus and related method
US20010015380A1 (en) * 1995-12-18 2001-08-23 Timothy A. Good Automated system for identifying and dimensioning packages transported through a laser scanning tunnel using laser scanning beam indexing techniques
US6283260B1 (en) * 2000-01-04 2001-09-04 Kenneth E. Yasuda, Sr. Storage device
US20010032034A1 (en) * 2000-04-12 2001-10-18 Hudson Soft Co. Ltd. Baggage managing system in airport
US6335688B1 (en) * 1999-09-28 2002-01-01 Clifford Sweatte Method and system for airport security
US6335960B2 (en) * 1999-10-18 2002-01-01 General Mills, Inc. Detection of variable manufacturing tolerance packages utilizing x-rays
US6345113B1 (en) * 1999-01-12 2002-02-05 Analogic Corporation Apparatus and method for processing object data in computed tomography data using object projections
US6359886B1 (en) * 1998-08-17 2002-03-19 Compaq Computer Corporation Method and apparatus for filtering and routing communications frames
US6364365B1 (en) * 1999-05-19 2002-04-02 Frances J. Caplan Personal luggage identification system and methods for use
US6370222B1 (en) * 1999-02-17 2002-04-09 Ccvs, Llc Container contents verification
US20020040928A1 (en) * 2000-10-11 2002-04-11 Reza Jalili Luggage-to-passenger match verification device
US20020069293A1 (en) * 2000-07-14 2002-06-06 Natalio Emer B. Method to distribute information in an airport
US20020107714A1 (en) * 2001-02-06 2002-08-08 Whitlock Steve Alexander Method and system fo transferring connecting baggage
US20020116550A1 (en) * 2000-09-22 2002-08-22 Hansen James R. Retrieving data from a server
US20020134836A1 (en) * 2001-03-23 2002-09-26 Cash Jerome E. Systems and methods for event driven baggage management
US6460681B1 (en) * 1997-02-05 2002-10-08 W & H Systems System for sorting articles using a double carrying tray
US6507278B1 (en) * 2000-06-28 2003-01-14 Adt Security Services, Inc. Ingress/egress control system for airport concourses and other access controlled areas
US6512964B1 (en) * 2000-09-20 2003-01-28 Baggagedirect.Com, Inc. Baggage transportation method
US20030023592A1 (en) * 2001-07-27 2003-01-30 Rapiscan Security Products (Usa), Inc. Method and system for certifying operators of x-ray inspection systems
US6546072B1 (en) * 1999-07-30 2003-04-08 American Science And Engineering, Inc. Transmission enhanced scatter imaging
US20030085281A1 (en) * 1999-06-07 2003-05-08 Knowles C. Harry Tunnel-type package identification system having a remote image keying station with an ethernet-over-fiber-optic data communication link
US20030085163A1 (en) * 2001-10-01 2003-05-08 Chan Chin F. Remote data access
US20030100973A1 (en) * 2000-09-20 2003-05-29 Steve Quackenbush Baggage transportation security system and method
US6580778B2 (en) * 2001-05-23 2003-06-17 Heimann Systems Gmbh Inspection device
US20030115340A1 (en) * 2001-10-31 2003-06-19 Sagula Rafael Linden Data transmission process and system
US20030118151A1 (en) * 2000-12-20 2003-06-26 Wido Menhardt Image reconstruction using multiple X-ray projections
US20030128806A1 (en) * 2001-09-29 2003-07-10 Laurence Morrell Baggage screening system
US20030127511A1 (en) * 2001-10-22 2003-07-10 Kelly Patrick J. Method and apparatus for providing heightened airport security
US20030128100A1 (en) * 2001-11-26 2003-07-10 Aero-Vision Technologies, Inc. System and method for monitoring individuals and objects associated with wireless identification tags
US20030137415A1 (en) * 2002-01-22 2003-07-24 Thomson James D. Homeland security emergency notification system
US20030141411A1 (en) * 2002-01-31 2003-07-31 Ashish Pandya Novel method to secure airline travel
US20030147484A1 (en) * 2001-11-08 2003-08-07 Olshansky Yury Iosiphovich Method for detecting an explosive in an object under investigation
US20030152186A1 (en) * 2002-01-28 2003-08-14 Jurczyk Brian E. Gas-target neutron generation and applications
US20030156679A1 (en) * 2002-02-19 2003-08-21 Kabushiki Kaisha Toshiba X-ray CT scanner capable of performing improved log conversion
US20040001568A1 (en) * 2002-06-03 2004-01-01 Lockheed Martin Corporation System and method for detecting alteration of objects
US20040010697A1 (en) * 2002-03-13 2004-01-15 Conor White Biometric authentication system and method
US20040017887A1 (en) * 2002-07-23 2004-01-29 Khai Le Self-contained, portable inspection system and method
US20040021572A1 (en) * 2002-08-05 2004-02-05 Schoen Marc L. Electronic baggage tracking and identification
US20040027376A1 (en) * 2002-08-08 2004-02-12 Calder Dale E. Displaying information over multiple user interface (UI) views
US20040036623A1 (en) * 2000-10-11 2004-02-26 Chung Kevin Kwong-Tai Tracking system and method employing plural smart tags
US6707879B2 (en) * 2001-04-03 2004-03-16 L-3 Communications Security And Detection Systems Remote baggage screening system, software and method
US20040054550A1 (en) * 2002-04-04 2004-03-18 James Cole System and method for the distribution of information during irregular operations
US20040120454A1 (en) * 2002-10-02 2004-06-24 Michael Ellenbogen Folded array CT baggage scanner
US6757714B1 (en) * 2000-07-28 2004-06-29 Axeda Systems Operating Company, Inc. Reporting the state of an apparatus to a remote computer
US20040148571A1 (en) * 2003-01-27 2004-07-29 Lue Vincent Wen-Jeng Method and apparatus for adapting web contents to different display area
US6789660B1 (en) * 1998-06-23 2004-09-14 Crisplant A/S Conveyor system with buffer arrangement
US6791487B1 (en) * 2003-03-07 2004-09-14 Honeywell International Inc. Imaging methods and systems for concealed weapon detection
US20050028091A1 (en) * 2003-07-30 2005-02-03 International Business Machines Corporation Method, system and recording medium for maintaining the order of nodes in a heirarchical document
US20050036470A1 (en) * 2003-08-04 2005-02-17 Calvert Nathan Hunter Multi-hop peer-to-peer wireless local loop phone system and method
US20050110672A1 (en) * 2003-10-10 2005-05-26 L-3 Communications Security And Detection Systems, Inc. Mmw contraband screening system
US6922460B2 (en) * 2003-06-11 2005-07-26 Quantum Magnetics, Inc. Explosives detection system using computed tomography (CT) and quadrupole resonance (QR) sensors
US20050190061A1 (en) * 2002-11-20 2005-09-01 Trela Richard S. Anti terrorist and homeland security public safety warning system
US6946300B2 (en) * 2002-02-01 2005-09-20 Control Screening, Llc Multi-modal detection of explosives, narcotics, and other chemical substances
US20050206514A1 (en) * 2004-03-19 2005-09-22 Lockheed Martin Corporation Threat scanning machine management system
US6982960B2 (en) * 2001-03-09 2006-01-03 Motorola, Inc. Protocol for self-organizing network using a logical spanning tree backbone
US7027773B1 (en) * 1999-05-28 2006-04-11 Afx Technology Group International, Inc. On/off keying node-to-node messaging transceiver network with dynamic routing and configuring
US7046134B2 (en) * 2002-06-27 2006-05-16 Axeda Corporation Screen sharing
US7082460B2 (en) * 2002-04-19 2006-07-25 Axeda Corporation Configuring a network gateway
US7106826B2 (en) * 2002-01-07 2006-09-12 Cdex, Inc. System and method for adapting a software control in an operating environment
US20060208871A1 (en) * 2003-06-27 2006-09-21 Hansen James R Screen sharing
US20070011349A1 (en) * 2005-06-09 2007-01-11 Lockheed Martin Corporation Information routing in a distributed environment
US7270227B2 (en) * 2003-10-29 2007-09-18 Lockheed Martin Corporation Material handling system and method of use
US7317390B2 (en) * 2003-06-11 2008-01-08 Quantum Magnetics, Inc. Screening checkpoint for passengers and baggage

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE2107489C3 (en) 1971-02-17 1975-02-27 Mannesmann Ag, 4000 Duesseldorf Pallet conveyor system for hand luggage at airports
DE3007130C2 (en) 1980-02-26 1983-12-08 Ikarus Karosszéria- és Jármügyár, Budapest Flight handling system for airports
US4879735A (en) 1988-05-31 1989-11-07 Owens Robert W Baggage inspection conveyor baffle and method
FR2652651B1 (en) 1989-10-03 1991-12-13 Commissariat Energie Atomique SYSTEM FOR DETECTION OF SUBSTANCES AND IN PARTICULAR EXPLOSIVES, BY NEUTRONIC IRRADIATION THEREOF.
US5367552A (en) 1991-10-03 1994-11-22 In Vision Technologies, Inc. Automatic concealed object detection system having a pre-scan stage
NZ237767A (en) 1992-04-09 1994-09-27 Inst Geolog Nuclear Sciences Luggage scanning by fast neutrons and gamma radiation
US5363951A (en) 1993-05-17 1994-11-15 Jervis B. Webb Company Over and under belt conveyor system
US5991764A (en) 1997-03-12 1999-11-23 International Business Machines Corporation Data structure specifying differing fan-in tree and fan-out tree computation patterns supporting a generic reduction object for data parallelism
US6158658A (en) 1997-08-27 2000-12-12 Laser Data Command, Inc. System and method for matching passengers and their baggage
US6145653A (en) 1997-09-22 2000-11-14 Jervis B. Webb Company Side by side belt conveyor system and method of use
WO1999030993A2 (en) 1997-12-12 1999-06-24 Crisplant A/S A conveyer system and a method for operating same
CA2346932A1 (en) 1998-10-20 2000-04-27 Alan J. Risi Security entrance system
US6487081B2 (en) * 2000-12-29 2002-11-26 Compaq Information Technologies Group, L.P. Hard disk drive mounting system and method
IL158190A0 (en) 2001-04-03 2004-03-28 L 3 Comm Security & Detection X-ray inspection system
DE10132816A1 (en) 2001-05-31 2002-12-05 Philips Corp Intellectual Pty Device and method for adjusting the radiation dose of an X-ray source
EP1395887A2 (en) 2001-06-07 2004-03-10 Siemens Aktiengesellschaft Tiered control architecture for material handling
US6608882B2 (en) 2001-06-13 2003-08-19 Surebeam Corporation System for, and method of, irradiating articles particularly articles with variable dimensions
US20020198731A1 (en) 2001-06-26 2002-12-26 Barnes Jessica M. Method and apparatus for processing an international passenger
US6668990B2 (en) 2002-03-12 2003-12-30 Norman John Humiston, Jr. Easily inspectable luggage
US6856344B2 (en) 2002-04-02 2005-02-15 Robert H. Franz Vehicle undercarriage inspection and imaging method and system
US20030189094A1 (en) 2002-04-09 2003-10-09 Trabitz Eugene L. Baggage tracking system
US7071823B2 (en) * 2002-04-24 2006-07-04 Brian Boesch System and method for centralized security screening
US7245315B2 (en) 2002-05-20 2007-07-17 Simmonds Precision Products, Inc. Distinguishing between fire and non-fire conditions using cameras
US6637563B1 (en) 2002-07-11 2003-10-28 Donald W. Ruckh Clear plastic case for moving through an airport
US6970088B2 (en) 2002-10-17 2005-11-29 Compex, Inc. Method for tracking and processing passengers and their transported articles
US6952163B2 (en) * 2003-06-11 2005-10-04 Quantum Magnetics, Inc. Combined systems user interface for centralized monitoring of a screening checkpoint for passengers and baggage

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3678278A (en) * 1970-01-26 1972-07-18 Le Roy E Peil Apparatus for baggage inspection
US3695462A (en) * 1970-08-28 1972-10-03 Rapistan Inc Baggage handling system
US3666073A (en) * 1971-02-19 1972-05-30 Mannesmann Geisel Gmbh Airport check-in counter with baggage receiving and handling facility
US3735853A (en) * 1972-03-01 1973-05-29 G Lingg System for distributing pieces of load such as baggage, parcels etc.
US4137567A (en) * 1974-10-24 1979-01-30 Grube Hans J System for passenger and luggage processing at commercial airports
US4210811A (en) * 1975-11-03 1980-07-01 Heimann Gmbh Drive for moveable shield in luggage screening apparatus
US4471039A (en) * 1982-11-22 1984-09-11 Eastman Kodak Company Photoconductive elements sensitive to radiation in the infrared region of the spectrum
US4604704A (en) * 1984-09-10 1986-08-05 Doboy Packaging Machinery, Inc. High-speed microprocessor-controlled branch conveyor
US4634849A (en) * 1985-04-02 1987-01-06 Klingen Leonard G Uniquely numbered baggage split tag and system for handling baggage
US5153439A (en) * 1987-05-26 1992-10-06 Science Applications International Corporation Multi-sensor explosive detection system using an articifical neural system
US5490218A (en) * 1990-08-10 1996-02-06 Vivid Technologies, Inc. Device and method for inspection of baggage and other objects
US5182764A (en) * 1991-10-03 1993-01-26 Invision Technologies, Inc. Automatic concealed object detection system having a pre-scan stage
US5802289A (en) * 1992-12-21 1998-09-01 Apple Computer, Inc. Method for propagating preemptive bus initialization on an acyclic directed graph
US5600303A (en) * 1993-01-15 1997-02-04 Technology International Incorporated Detection of concealed explosives and contraband
US5600700A (en) * 1995-09-25 1997-02-04 Vivid Technologies, Inc. Detecting explosives or other contraband by employing transmitted and scattered X-rays
US5642393A (en) * 1995-09-26 1997-06-24 Vivid Technologies, Inc. Detecting contraband by employing interactive multiprobe tomography
US5793639A (en) * 1995-10-24 1998-08-11 Toyota Jidosha Kabushiki Kaisha Baggage receiving and handling method in airport, baggage receiving and handling system in airport, and baggage automatic handling apparatus
US6018562A (en) * 1995-11-13 2000-01-25 The United States Of America As Represented By The Secretary Of The Army Apparatus and method for automatic recognition of concealed objects using multiple energy computed tomography
US20010015380A1 (en) * 1995-12-18 2001-08-23 Timothy A. Good Automated system for identifying and dimensioning packages transported through a laser scanning tunnel using laser scanning beam indexing techniques
US5870449A (en) * 1996-05-08 1999-02-09 Vivid Technologies, Inc. Operator console for article inspection systems
US5910973A (en) * 1996-07-22 1999-06-08 American Science And Engineering, Inc. Rapid X-ray inspection system
US5796802A (en) * 1996-08-19 1998-08-18 Analogic Corporation Multiple angle pre-screening tomographic systems and methods
US5974111A (en) * 1996-09-24 1999-10-26 Vivid Technologies, Inc. Identifying explosives or other contraband by employing transmitted or scattered X-rays
US6222452B1 (en) * 1996-12-16 2001-04-24 Confidence International Ab Electronic identification tag
US5920053A (en) * 1997-01-06 1999-07-06 Debrouse; Cynthia R. Passenger identification and baggage control system
US6460681B1 (en) * 1997-02-05 2002-10-08 W & H Systems System for sorting articles using a double carrying tray
US5949842A (en) * 1997-10-10 1999-09-07 Analogic Corporation Air calibration scan for computed tomography scanner with obstructing objects
US5970113A (en) * 1997-10-10 1999-10-19 Analogic Corporation Computed tomography scanning apparatus and method with temperature compensation for dark current offsets
US6256404B1 (en) * 1997-10-10 2001-07-03 Analogic Corporation Computed tomography scanning apparatus and method using adaptive reconstruction window
US6014628A (en) * 1997-11-03 2000-01-11 Exigent International, Inc. Method and system for tracking any entity through any set of processes utilizing a temporal projection
US6044353A (en) * 1998-03-10 2000-03-28 Pugliese, Iii; Anthony V. Baggage check-in and security system and method
US6218943B1 (en) * 1998-03-27 2001-04-17 Vivid Technologies, Inc. Contraband detection and article reclaim system
US6088423A (en) * 1998-06-05 2000-07-11 Vivid Technologies, Inc. Multiview x-ray based system for detecting contraband such as in baggage
US6789660B1 (en) * 1998-06-23 2004-09-14 Crisplant A/S Conveyor system with buffer arrangement
US6359886B1 (en) * 1998-08-17 2002-03-19 Compaq Computer Corporation Method and apparatus for filtering and routing communications frames
US6265977B1 (en) * 1998-09-11 2001-07-24 Motorola, Inc. Radio frequency identification tag apparatus and related method
US6230043B1 (en) * 1998-09-30 2001-05-08 General Electric Company Method and apparatus for capturing and automatically transferring an x-ray image to a remote location
US6345113B1 (en) * 1999-01-12 2002-02-05 Analogic Corporation Apparatus and method for processing object data in computed tomography data using object projections
US6370222B1 (en) * 1999-02-17 2002-04-09 Ccvs, Llc Container contents verification
US6364365B1 (en) * 1999-05-19 2002-04-02 Frances J. Caplan Personal luggage identification system and methods for use
US7027773B1 (en) * 1999-05-28 2006-04-11 Afx Technology Group International, Inc. On/off keying node-to-node messaging transceiver network with dynamic routing and configuring
US20030085281A1 (en) * 1999-06-07 2003-05-08 Knowles C. Harry Tunnel-type package identification system having a remote image keying station with an ethernet-over-fiber-optic data communication link
US6546072B1 (en) * 1999-07-30 2003-04-08 American Science And Engineering, Inc. Transmission enhanced scatter imaging
US6335688B1 (en) * 1999-09-28 2002-01-01 Clifford Sweatte Method and system for airport security
US6335960B2 (en) * 1999-10-18 2002-01-01 General Mills, Inc. Detection of variable manufacturing tolerance packages utilizing x-rays
US6283260B1 (en) * 2000-01-04 2001-09-04 Kenneth E. Yasuda, Sr. Storage device
US20010032034A1 (en) * 2000-04-12 2001-10-18 Hudson Soft Co. Ltd. Baggage managing system in airport
US6594547B2 (en) * 2000-04-12 2003-07-15 Hudson Soft Co., Ltd. Baggage managing system in airport
US6507278B1 (en) * 2000-06-28 2003-01-14 Adt Security Services, Inc. Ingress/egress control system for airport concourses and other access controlled areas
US20020069293A1 (en) * 2000-07-14 2002-06-06 Natalio Emer B. Method to distribute information in an airport
US20040177124A1 (en) * 2000-07-28 2004-09-09 Hansen James R. Reporting the state of an apparatus to a remote computer
US6757714B1 (en) * 2000-07-28 2004-06-29 Axeda Systems Operating Company, Inc. Reporting the state of an apparatus to a remote computer
US20030100973A1 (en) * 2000-09-20 2003-05-29 Steve Quackenbush Baggage transportation security system and method
US6512964B1 (en) * 2000-09-20 2003-01-28 Baggagedirect.Com, Inc. Baggage transportation method
US20020116550A1 (en) * 2000-09-22 2002-08-22 Hansen James R. Retrieving data from a server
US20040036623A1 (en) * 2000-10-11 2004-02-26 Chung Kevin Kwong-Tai Tracking system and method employing plural smart tags
US20020040928A1 (en) * 2000-10-11 2002-04-11 Reza Jalili Luggage-to-passenger match verification device
US20030118151A1 (en) * 2000-12-20 2003-06-26 Wido Menhardt Image reconstruction using multiple X-ray projections
US20020107714A1 (en) * 2001-02-06 2002-08-08 Whitlock Steve Alexander Method and system fo transferring connecting baggage
US6982960B2 (en) * 2001-03-09 2006-01-03 Motorola, Inc. Protocol for self-organizing network using a logical spanning tree backbone
US20020134836A1 (en) * 2001-03-23 2002-09-26 Cash Jerome E. Systems and methods for event driven baggage management
US6707879B2 (en) * 2001-04-03 2004-03-16 L-3 Communications Security And Detection Systems Remote baggage screening system, software and method
US6721391B2 (en) * 2001-04-03 2004-04-13 L-3 Communications Security And Detection Systems Remote baggage screening system, software and method
US20050031076A1 (en) * 2001-04-03 2005-02-10 L-3 Communications Security And Detections System Remote baggage screening method
US6580778B2 (en) * 2001-05-23 2003-06-17 Heimann Systems Gmbh Inspection device
US20030023592A1 (en) * 2001-07-27 2003-01-30 Rapiscan Security Products (Usa), Inc. Method and system for certifying operators of x-ray inspection systems
US20030128806A1 (en) * 2001-09-29 2003-07-10 Laurence Morrell Baggage screening system
US20030085163A1 (en) * 2001-10-01 2003-05-08 Chan Chin F. Remote data access
US20030127511A1 (en) * 2001-10-22 2003-07-10 Kelly Patrick J. Method and apparatus for providing heightened airport security
US20030115340A1 (en) * 2001-10-31 2003-06-19 Sagula Rafael Linden Data transmission process and system
US20030147484A1 (en) * 2001-11-08 2003-08-07 Olshansky Yury Iosiphovich Method for detecting an explosive in an object under investigation
US20030128100A1 (en) * 2001-11-26 2003-07-10 Aero-Vision Technologies, Inc. System and method for monitoring individuals and objects associated with wireless identification tags
US7106826B2 (en) * 2002-01-07 2006-09-12 Cdex, Inc. System and method for adapting a software control in an operating environment
US20030137415A1 (en) * 2002-01-22 2003-07-24 Thomson James D. Homeland security emergency notification system
US20030152186A1 (en) * 2002-01-28 2003-08-14 Jurczyk Brian E. Gas-target neutron generation and applications
US20030141411A1 (en) * 2002-01-31 2003-07-31 Ashish Pandya Novel method to secure airline travel
US6946300B2 (en) * 2002-02-01 2005-09-20 Control Screening, Llc Multi-modal detection of explosives, narcotics, and other chemical substances
US20030156679A1 (en) * 2002-02-19 2003-08-21 Kabushiki Kaisha Toshiba X-ray CT scanner capable of performing improved log conversion
US20040010697A1 (en) * 2002-03-13 2004-01-15 Conor White Biometric authentication system and method
US20040054550A1 (en) * 2002-04-04 2004-03-18 James Cole System and method for the distribution of information during irregular operations
US7082460B2 (en) * 2002-04-19 2006-07-25 Axeda Corporation Configuring a network gateway
US20040001568A1 (en) * 2002-06-03 2004-01-01 Lockheed Martin Corporation System and method for detecting alteration of objects
US7046134B2 (en) * 2002-06-27 2006-05-16 Axeda Corporation Screen sharing
US20040017887A1 (en) * 2002-07-23 2004-01-29 Khai Le Self-contained, portable inspection system and method
US20040021572A1 (en) * 2002-08-05 2004-02-05 Schoen Marc L. Electronic baggage tracking and identification
US20040027376A1 (en) * 2002-08-08 2004-02-12 Calder Dale E. Displaying information over multiple user interface (UI) views
US20040120454A1 (en) * 2002-10-02 2004-06-24 Michael Ellenbogen Folded array CT baggage scanner
US20050190061A1 (en) * 2002-11-20 2005-09-01 Trela Richard S. Anti terrorist and homeland security public safety warning system
US20040148571A1 (en) * 2003-01-27 2004-07-29 Lue Vincent Wen-Jeng Method and apparatus for adapting web contents to different display area
US6791487B1 (en) * 2003-03-07 2004-09-14 Honeywell International Inc. Imaging methods and systems for concealed weapon detection
US6922460B2 (en) * 2003-06-11 2005-07-26 Quantum Magnetics, Inc. Explosives detection system using computed tomography (CT) and quadrupole resonance (QR) sensors
US7317390B2 (en) * 2003-06-11 2008-01-08 Quantum Magnetics, Inc. Screening checkpoint for passengers and baggage
US20060208871A1 (en) * 2003-06-27 2006-09-21 Hansen James R Screen sharing
US20050028091A1 (en) * 2003-07-30 2005-02-03 International Business Machines Corporation Method, system and recording medium for maintaining the order of nodes in a heirarchical document
US20050036470A1 (en) * 2003-08-04 2005-02-17 Calvert Nathan Hunter Multi-hop peer-to-peer wireless local loop phone system and method
US20050110672A1 (en) * 2003-10-10 2005-05-26 L-3 Communications Security And Detection Systems, Inc. Mmw contraband screening system
US7270227B2 (en) * 2003-10-29 2007-09-18 Lockheed Martin Corporation Material handling system and method of use
US20050206514A1 (en) * 2004-03-19 2005-09-22 Lockheed Martin Corporation Threat scanning machine management system
US20070011349A1 (en) * 2005-06-09 2007-01-11 Lockheed Martin Corporation Information routing in a distributed environment

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7734102B2 (en) 2005-05-11 2010-06-08 Optosecurity Inc. Method and system for screening cargo containers
US7991242B2 (en) 2005-05-11 2011-08-02 Optosecurity Inc. Apparatus, method and system for screening receptacles and persons, having image distortion correction functionality
US7684421B2 (en) 2005-06-09 2010-03-23 Lockheed Martin Corporation Information routing in a distributed environment
US7899232B2 (en) 2006-05-11 2011-03-01 Optosecurity Inc. Method and apparatus for providing threat image projection (TIP) in a luggage screening system, and luggage screening system implementing same
US8494210B2 (en) 2007-03-30 2013-07-23 Optosecurity Inc. User interface for use in security screening providing image enhancement capabilities and apparatus for implementing same
US10422919B2 (en) 2011-09-07 2019-09-24 Rapiscan Systems, Inc. X-ray inspection system that integrates manifest data with imaging/detection processing
US9632206B2 (en) 2011-09-07 2017-04-25 Rapiscan Systems, Inc. X-ray inspection system that integrates manifest data with imaging/detection processing
US10509142B2 (en) 2011-09-07 2019-12-17 Rapiscan Systems, Inc. Distributed analysis x-ray inspection methods and systems
US10830920B2 (en) 2011-09-07 2020-11-10 Rapiscan Systems, Inc. Distributed analysis X-ray inspection methods and systems
US11099294B2 (en) 2011-09-07 2021-08-24 Rapiscan Systems, Inc. Distributed analysis x-ray inspection methods and systems
US9621572B2 (en) * 2013-03-15 2017-04-11 Cyber Engineering Services, Inc. Storage appliance and threat indicator query framework
US20140283075A1 (en) * 2013-03-15 2014-09-18 Cyber Engineering Services, Inc. Storage appliance and threat indicator query framework
US10302807B2 (en) 2016-02-22 2019-05-28 Rapiscan Systems, Inc. Systems and methods for detecting threats and contraband in cargo
US10768338B2 (en) 2016-02-22 2020-09-08 Rapiscan Systems, Inc. Systems and methods for detecting threats and contraband in cargo
US11287391B2 (en) 2016-02-22 2022-03-29 Rapiscan Systems, Inc. Systems and methods for detecting threats and contraband in cargo

Also Published As

Publication number Publication date
US20050206514A1 (en) 2005-09-22
US7183906B2 (en) 2007-02-27

Similar Documents

Publication Publication Date Title
US7183906B2 (en) Threat scanning machine management system
US7212113B2 (en) Passenger and item tracking with system alerts
US20050251397A1 (en) Passenger and item tracking with predictive analysis
US20050251398A1 (en) Threat scanning with pooled operators
CN102035855B (en) Network security incident association analysis system
US10021138B2 (en) Policy/rule engine, multi-compliance framework and risk remediation
US20170331709A1 (en) Remote system data collection and analysis framework
US10019677B2 (en) Active policy enforcement
US8769412B2 (en) Method and apparatus for risk visualization and remediation
da Silva Avanzi et al. A framework for interoperability assessment in crisis management
AU2002303207B2 (en) A remote baggage screening system, software and method
CN107317718B (en) A kind of O&M service management and management platform
AU2002303207A1 (en) A remote baggage screening system, software and method
CN104820804A (en) Online privacy management
WO2007046844A2 (en) System and method for visual representation of a catastrophic event and coordination of response
CN107577947A (en) Leak detection method, system, storage medium and the electronic equipment of information system
US9915929B1 (en) Monitoring availability of facility equipment
KR20060058186A (en) Information technology risk management system and method the same
Reuschling et al. Toolkit to enhance cyberphysical security of critical infrastructures in air transport
CN113282474A (en) User behavior monitoring method, system, equipment and medium based on bastion machine
Gkotsis et al. Solutions for protecting the space ground segments: From risk assessment to emergency response
da Silva Avanzi et al. Journal of Industrial Information Integration
Wang et al. Visualization for anomaly detection and data management by leveraging network, sensor and GIS techniques
Bukirwa et al. Forest auditory surveillance system
KR20230015571A (en) Integrated workplace accident control system and method thereof

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE