Auto Bag Drop Application Architecture Common Use Self Service (CUSS) Architecture May 2014 Page 1 of 13 #ABD0000 ICM Airport Technics Australia Pty Ltd Commercial in Confidence
Contents 1. Architecture Overview... 3 1.1. Pre-CUSS ABD Platform... 4 1.2. CUSS Standard... 4 1.3. CORBA Technology... 5 2. ABD CUSS Platform... 6 2.1. CUSS Software Platform... 6 2.2. CUSS Auto Bag Drop Application... 7 2.3. Hardware Platform... 7 2.4. Airline Application Server(s) or Host(s)... 7 2.5. Bag Drop Server (BDS)... 7 2.6. ICM ABD System Manager... 7 2.7. CUSS Interfaces... 8 3. Generic CUSS ABD Application...10 3.1. User Friendly System...10 3.2. Airline Adapter Module...10 3.3. Configurable Branding...10 4. ICM Auto Bag Drop Benefits... 11 4.1. Reporting System... 11 4.2. Safe and Secure...12 4.3. Fast and Efficient...12 4.4. Flexible Integration...12 4.5. Mix and Match...12
1. Architecture Overview ICM s Auto Bag Drop architecture is multi-tiered comprised of the ABD Client, the Bag Drop Server, the ABD System Manager server and the airline Departure Control System (DCS). The Bag Drop Server provides communications between the DCS host and a number of ABD Clients and contains the multi- airline business logic decisions. The ABD System Manager server monitors both the ABD hardware and the applications, providing the appropriate information, access and control to authorised personnel. The ABD application provides the end-user functionality that the ABD offers to the passenger for baggage drop off.
1.1. Pre-CUSS ABD Platform The pre-cuss Auto Bag Drop environment consists of a multi-tier architecture with hardware devices running on a Windows platform and a Common Application capable of handling multiple airlines. The Bag Drop Server (BDS) handles the communications and interface to the airline Departure Control Systems (DCS). Airline Departure Control System (DCS) Airline Departure Control System (DCS) Airline Departure Control System (DCS) Bag Drop Server (BDS) Airline Adapter Airline Adapter Airline Adapter Bad Drop Server (BDS) Bag Drop Server hub Airline Adapter Bag Drop Application ABD Common Application Auto Bag Drop (ABD) Client Software Platform Application Launcher Multi Airline Application Windows Comm Interface Windows Operating System ICM ABD Support Manager Hardware Platform Auto Bag Drop Hardware Devices Proprietary Interface Baggage Handling System (BHS) 1.2. CUSS Standard The idea of CUSS (Common Use Self Service) was driven by the need for airlines to share checkin kiosks. It aimed to provide a standard to allow the same application to run on a broad range of kiosk hardware, without airlines having to support multiple versions of the same application. To achieve this cross-platform utilisation, and application interoperability the industry body responsible for the standard, IATA, turned to the IT industry standards of JAVA for the programming language and CORBA for the interfaces. Write-once, run anywhere, the mantra of Java, was borrowed by the IATA CUSS management team for the philosophy to underpin CUSS. Rather than mandate an application architecture, the team turned to CORBA, or Common Object Request Broker Architecture to provide secure
interoperability. Interoperability gives airline developers the flexibility to create applications as thin web-applications or fat clients to match their internal coding architectures. 1.3. CORBA Technology The CUSS standard uses CORBA to accomplish two major purposes. Firstly, it abstracts the intricacies of hardware away from the application developers. Secondly, it also standardizes a common set of services that are provided by a shared kiosk.the first purpose is extremely important to the success of CUSS - the standard defines a generic set of CORBA services for commonly used peripherals, such as printers, credit card readers, and passport scanners. CUSS establishes the concept of Virtual Device Components to shield developers from the myriad of proprietary device drivers and hardware specific idiosyncrasies. This clearly defined set of interfaces allows the creation of a single application, regardless of the hardware implementation.
2. ABD CUSS Platform The diagram below shows the various components of the ABD environment. Airline Departure Control System (DCS) Airline Departure Control System (DCS) Airline Departure Control System (DCS) Bag Drop Server (BDS) Application Server or Host Airline Airline Airline Adapter Adapter Adapter Bag Drop Server hub Bag Drop Application Airline Application Airline Application Airline Applications Generic CUSS ABD Application CORBA Interface Auto Bag Drop (ABD) Client Software Platform Application Manager ABD CUSS Platform Common Launch Application Device Components System Manager Interface ICM ABD System Manager Integrated Baggage System Conveyor (AEA-SBD) CUSS traditional Virtual Device Components Proprietary or AEA Interface (depending on Device) Hardware Platform Auto Bag Drop Hardware Devices Proprietary Interface Baggage Handling System (BHS) The CUSS environment is divided into two domains. One domain is the CUSS Software Platform and the other domain is part of the private environment of the CUSS Bag Drop Application. The orange arrows reflect the interfaces that comply with the CUSS standard. 2.1. CUSS Software Platform The platform software consists of all the software included in the auto bag drop client except the ABD application. These are the Application Manager, the System Manager Interface, the
Common Launch Application and the Device Components. Together, these platform elements are responsible for managing the entire Auto Bag Drop system including: Instantiation and presentation of all platform processes including browser and device components Displaying common screens while no bag drop application is active Providing data and statistical information to the remote management system via the system manager interface Controlling/monitoring components states Managing system security These responsibilities are shared by various platform elements, namely, the platform environment, the application manager, the system manager interface, the common launch application, and the device components. See the section, CUSS Interfaces, for a description of these elements in more details. 2.2. CUSS Auto Bag Drop Application The auto bag drop application is run on the client and communicates with the CUSS platform (Application Manager and Device Components) via the CUSS interface. 2.3. Hardware Platform CUSS Platform hardware consists of all hardware components included in the auto bag drop client. This currently includes a Personal Computer, Touch Screen, Conveyor Belt, Receipt Printer, Boarding Pass Reader, Bag Tag Reader, and optional components such as RFID Scanner/Reader and 3D Scanners and Cameras. 2.4. Airline Application Server(s) or Host(s) Most airline bag drop applications might do backend communication with servers or hosts in their application provider's environment (e.g. airline departure control systems (DCS)). 2.5. Bag Drop Server (BDS) The Bag Drop Server contains the server components for the Generic CUSS ABD Application as well as the individual airline adapters to interface to the airline Departure Control Systems. 2.6. ICM ABD System Manager The ABD System Manager is used to retrieve system management information from the Auto Bag Drop. It communicates with the CUSS platform (System Manager Interface and Device
Components) via the CUSS interface. It is used to control the applications running on the platform as well as providing diagnostic and reporting services. 2.7. CUSS Interfaces It is the ABD client where the implementation conforms to the IATA CUSS standard. There are three defined platform interfaces: Device Components Interface, Application Manager Interface, and System Manager Interface. 2.7.1. Device Components Interface The ABD application is not allowed to access the hardware devices directly. To realise this, the CUSS standard introduces a hardware abstraction layer that hides the proprietary device interfaces from the ABD application. The ABD application accesses the hardware devices through the device component interfaces of the platform. The ICM CUSS Platform will include support for both types of device interfaces mandated by CUSS 1.3 to access the Integrated Baggage System Conveyor extended device: AEA-SBD allows complete control using the AEA2012-2 specification for bag drop devices CUSS-SBD allows complete control using the CUSS traditional virtual component model 2.7.2. Application Manager Interface The application manager is responsible for controlling and scheduling the ABD applications which are registered on a specific ABD. Applications decide whether to become available (selectable on the Common Launch screen) or not available (not selectable on the Common Launch screen), and tell the application manager accordingly. The application manager also polices the applications and makes sure that they are not misbehaving! Only the active application is allowed to access the ABD s device components; this access is managed via the CUSS interfaces by the CUSS platform. During idle times, while no other CUSS application is running, the Common Launch Application is activated by the CUSS application manager. 2.7.3. System Manager Interface The system manager interface allows for remote management of the ABD. It is a standard CORBA interface implemented on the ABD, allowing for remote connection from authorised system managers. Functionality includes: Reporting errors, alerts and alarms encountered by device components. Reporting of platform events such as application state changes, application events, etc.
Gathering statistical information (Some of this is for the ABD owner, some for the application owner). Remote control of the application load/stop/suspend/resume.
3. Generic CUSS ABD Application 3.1. User Friendly System Our Auto Bag Drop uses a simple, intuitive graphical user interface which is easily configurable for specific airline requirements and branding. Baggage is automatically checked by determining the bag weight, dimensions, volume, shape, conveyability and RFID &/or barcode bag tag, all on the first belt. Processing can be completed in as little as 10 seconds. Our secure Agent Assist mode can be used to handle exceptions and for Business Continuity Processing (BCP) mode. 3.2. Airline Adapter Module Our modular design allows integration to multiple Departure Control Systems (DCS) using our Airline Adapter modules. Using these modules allows easy integration with no or minimal host changes. This approach also allows specific local based workflow to supplement the DCS based rules. 3.3. Configurable Branding Our Auto Bag Drop application can be easily configured to suit the branding requirements of different airlines. We have already accommodated the requirements of Qantas and British Airways within the same application with respect to the following configurable items: Company Logo Alliance Logo Animations Wording of Messages Language Selection
4. ICM Auto Bag Drop Benefits 4.1. Reporting System The Auto Bag Drop Reporting System uses metrics logged in the BDS database to generate various types of graphical as well as tabular reports. These reports are invaluable for monitoring the operation of the Auto Bag Drops, for management reporting, and for system tuning. The following reports are available: Transaction Time Report - Per Day / Hour / Minute Transaction Time For Number of Bags Per ABD (ABDs on X-Axis) Report Customer Session Report - Per Day / Hour / Minute Total Bags Report - Per Day / Hour / Minute Availability States Report - Per Day / Hour SLA Availability Report Per Day / Hour Total Bags (ABDs on X-Axis) Report Availability States (ABDs on X-Axis) Report Heavy Tags Printed and Injected Per ABD (ABDs on X-Axis) Report Q Bag Tag Write Per ABD (ABDs on X-Axis) Report Q Bag Tag Read Per ABD (ABDs on X-Axis) Report Heavy Tag Read Per ABD (ABDs on X-Axis) Report Paper Tag Reads Per ABD (ABDs on X-Axis) Report Average Bag Dimensions Report Bag Rejection Rate Report Reports can be viewed on a Live Dashboard, printed, or can be exported as Excel or PDF documents. The Reporting System supports multiple access levels depending on the login role of the user: Airport Level: When assigned to this level, the user will have access to all available data; this data can also be used for billing purposes Airline Level: When assigned to this level the user can only access data specific to the airline associated with the user.
4.2. Safe and Secure Using patented technology, anti-intrusion systems prevent any kind of trapping or injury to passengers, as well as maintaining the integrity of the weighing process. Security is maintained by a series of light curtains used to detect intrusion by persons or objects entering the conveyor system. Non-conveyable and multiple bags are detected using advanced 3D analysis. Optional biometric systems can be readily integrated to meet airport and airline specific security requirements. 4.3. Fast and Efficient The Auto Bag Drop is designed for a two-stage check-in process which optimises the use of real estate in the airport departures concourse. The two-stage check-in process results in significant savings in both expenditure and footprint. All processes are conducted on the first belt resulting in fast transaction times and improved workflow processes. Excess baggage and heavy bags are efficiently processed based on airline requirements. 4.4. Flexible Integration Our Auto Bag Drop Series 1 and 3 are designed to be retrofitted into existing check-in desks, whereas our Series 5 and 7 models are designed to replace existing check-in desks. All models can be seamlessly integrated into the terminal design with interfaces into baggage handling, departure control, security and overhead display systems. ICM is closely following the IATA/ACI initiative to develop standardised web service definitions across the aviation ecosystem in order to support self-service bag drop processes. These standard interfaces will be incorporated within the ICM Auto Bag Drop solution as and when they become available. 4.5. Mix and Match Our solution is very modular and can be easily tailored to integrate modules sourced from multiple vendors. For example: The CUSS Auto Bag Drop Applications could be sourced from the airlines or other vendors; alternatively, the ICM Generic CUSS ABD Application could be used (with customised Branding) to support multiple airlines The ABD CUSS Platform components could be provided by ICM or could be sourced from another vendor ICM can also provide the Integrated Baggage System Conveyor (AEA-SBD) and all associated Hardware Devices and supporting infrastructure (Conveyor Belt,
Intrusion Detection Devices, 3D Baggage Scanner, PLC, SCADA, etc.) while all other CUSS Platform components are sourced from another vendor.