Service facts

• Name: BhsSubmitService BagInformationSubmitService

• Operations, see Service operations.

• REST based service. Operations are accessed using HTTPS POST.
• Service security: Decided by implementation.

• Standard return codes are described here: Service error response

Introduction

Overview

This service description defines one service with a set of operations designed to support the need airports have for bag related information from baggage handling systems (BHS). At the bag level this service slightly extend the functionality in the bixs, and adds functionality for reporting batch oriented events. A "batch" in this regard is a set of bags treated as one "unit" and delivered at some location without any other bags being delivered to the same location. operation to submit IATA Baggage Information Message information to the service provider. This makes it possible for the airport (provider) to receive IATA teletype baggage messages directly.

The service is designed to meet the need of a BHS Baggage Information Message provider.

A set of use cases are described here: Avinor Service use cases

The service is defined using ACI Data Dictionary terms. Naming of entities are service specific.

Implementation considerations

Any implementation of this service MUST use the XSD files provided here: XSDs

It is however up to the service provider which data elements to support.

Any service provider should make available documentation about the actual implementation, including:

• • the address of the service.
  • any limitations in the implementation.

Purpose of this service description

This service description has the following purpose:

• • • Describe of service in enough detail for a service provider to implement it.
    • Describe the service so that a client (of this service) developer can use it.
    • Make available the XSD files necessary to implement and use the service.
    • Make it possible for relevant people at airports, airlines, handlers and other aviation partners to understand the available functionality and then to decide if to implement/use it or not.

Intended readership

• • IT architects
  • Developers
  • Business architects
  • Interested parties in the aviation community

Service operations

Data entities

Service use cases

XSDs