Best Airport Cargo Handling System

BACH

CCS HUNGARY

BACH (Best Airport Cargo Handling) System is a revolutionary

design and we hope you will find the system as good as it

deserves to use the "Best" in its name.

Supports and satisfy the requirements of the latest trends and

standards like:

Introduction

• ISO/TQM

• Barcode/RFID

• Electronic archiving

• Paperless cargo

• SITA via Internet

• Client server architecture

• PC / Windows based

• Warnings can be found in the lower-left corner of the

window for users and supervisors also showing failures

and delays during the process giving exact,

understandable information about the problem

• System responses contain clear instructions for

problem-solving. BACH is controlling and training in the

same time the handling staff.

BACH main menu

The BACH (Best Airport Cargo Handling) System is designed to control export, import and transit air cargo shipments

Optional Flight Schedule Manager & Freight Reservations modules

Capable of multi-language working

Can be easily interpret any kind of language without program modification

System architecture

Operational

database

Archive

database

File SystemFirebird 1.5

SQL server

Client PC BachStartautomatic

upgrading

BachClientBachFax

Faxing notification

to customer

BachCodeControlling

barcode scanners

Barcodescanner

BachAmaArchiving

the database

BachServerSITA message

handling

Customs

connection

Reservations

database

PosgreSQLserver

Interfaceto flight planning

systemSchedule

databaseWindows server

Communication via SITA

SITAnetwork

SITA Gateway

server

SITA Gateway

application

Bach Server

computer

SITA

Daemon

BachServer

application

LAN

File

transaction

X-25

X-28

IP

AirlinesForwarders Agents

Other

handlingagents

Airline Flight Schedule module I.

• Any kind of flight-number (including non-IATA standard)

• Day change flights without day limitations

• Special flights (e.g. trucks, cargo only, offline, circle…)

Airline Flight Schedule module II.

Aircraft types, and codes

Aircraft limitations, warnings

Route/Flight limitations, warnings

FFM, FWB,

FSU

Warehouse location

(manual/ bar-code based)

Damage

report

Found

cargo

Documents:

Manifest, AWBs

Arrival

Departure

station

Create FAD

Document entry

Auto processing

Create FAD

Incoming cargo

Print bar-

coded labels

• Flight No

• MAWB

• Weight

• Piece

• ULD

• LocationCreate FAD

CCARate check

Freight acceptance to warehouse

Arrival document entry

FFM

data

Warehouse

data

Document

dataCompare

Finalize

Flight

Finalize arrival flight

Ready for

delivery

• This action is the most important step of the import process flow that is why its use

needs great care

• This is the time for second check and supervision - finalizing a flight it is declared

that all information of the actual flight are entered wholly & correctly

• Close a flight only when it is absolutely sure that all of the consignment records are

clear, the warehouse and document data differences are real for sure, the

consignees were chosen correctly etc.

• The best is if the senior, highest educated supervisor does it

• It is strongly recommended that a different person close the flight

than the one who entered the document data

After finalizing, the status information (FSU) and

the irregularity information (FAD) messages will be

sent automatically to the interested parties.

Ready for

manifestingTransit

shipments

Finalize the flight

FSU FAD

Sending out

SITA-msgs

Customs

registration

Consignee

notification

• FAX

• SITA

• Phone

Automatic process after flight close

FSU:

RCF,RCT,TFD,NFD,DLV

FAD:MSAW,MSCA,

FDAW,FDCA

EU

Transit

NO

N E

U

Calculation of other

added charges

TransferTransfer

manifest

Ready for

manifesting

Delivery procedure

Document

delivery

Freight

delivery

Individual

Group

Trucking

to door

Transfer to

forwarder,

warehouse

HAWB

splitting

HAWB

location

Delivery

Revenue accounting

Check auto-calculated

and manually entered

rates & charges

Print & send CCA

Accounting closing

Interface to

Interline accounting

Interface to

Agency accounting

Interface to

Invoicing module

INBOUND PROCESS

flow chart of the reservations proccess

Logical structure

of the reservations

module

Booking – Searching for the flight

Manipulate bookings (split, change…)

Booking completed

Warnings

• Help for the userwith information to

solve problems, errors…

• Help for the super-

visor to control theproccess…

• Real-time, creditable, valid information from the system

• To get the information You need: just a „click” to the warning

line and the adequate window pop up helps to handle the

problem as soon as possible

FFR message handling

Lying list – unbooked shipments

Finalize flight reservation

• This is the final phase of the reservation proccess

that is why its use needs a great care;

• Flight should be closed only, if it is absolutely sure

that all of the consignments data are valid, and

priority sequence is set correctly;

• After finalizing the flight FBL message will be sent

automatically;

• Optional adjustable automated finalization:

• Save human resources

• Reduce risk

Export freight/document handling

Freights

Storage to

warehouse

Full document

entry (FWB)

Express

document entry

• MAWB

• HAWB

• Pieces no.

• Weight

Return to

shipper

Delete

location

Warehouse

location

CCARates &

charges

check

Create AWB

(auto rate, auto price)

Print AWB

(laser-printed)

Warehouse

location

Document

exist?

Handling

Airline

Manifesting

Loading

ULD

Pre-manifest

flight

Print

pre-manifest(with locations)

Finalize

flight

Modify

manifest

Transfer

lists

Loading to

aircraft

Boo

ke

d o

r lyin

g s

hip

me

nts

or p

art s

hip

me

nts

Print

manifest

Source:Reservations

module,or

FBL MSG

from airlines

Finalizing departure flight

FSU FFM

Sending out

SITA-msgs

FSU types:

RCS,TFD,MANDEP

Calculation of

airline charges

FWB SLS

• This action is the most important step of the export flow that

is why its use needs great care

• Flight should be closed only, if it is absolutely sure that all of

the consignments data are clear, the warehouse data and air waybills are correct

• It can be declared with the finalizing of the flight, that the

information about the actual flight is correct and wholly entered

• Before the flight-finalizing it is possible to modify the list of

the consignments transported on the flight, with the help of pre-manifest flight function and reprint a modified manifest

• After finalizing the flight FFM, FSU, FWB, etc. messages will be sent automatically, and accounting procedure is starting

STM

Finalizing departure flight screen

Revenue accounting(same as import)

Check auto-calculated

and manually entered

rates & charges

Print & send CCA

Accounting closing

Interface to

Interline accounting

Interface to

Agency accounting

Interface to

Invoicing module

Reports, history, basic-data

History

Archive

mode

Reports

MAWB

HAWB

Flight

Customers

Warehouse

inventory

ULD list

Missing

messages

Customs

report

Export

customs list

Import

customs list

Arrival list

of date

Shipments

summary

Customers

list

Sales

reports

Barcodes

of location

Entering

freight WH

Ava

ilable

in E

xce

l/ Access fo

rma

t

Basic

Locations

Airports

Customers

Carriers

Users

Schedule

Customers

Messages & correctionsMessage centre

(for SITA msg handling)

Create

Edit

Reply

Forward

Search

Print

FWB

FFM

FBL

FSR

BEA

USR

FSA

FSU

TTY

Co

rrectio

ns

New location for

finalized import flight

Modify import flight

Import instead of

export

Open finalized

export flight

Air waybill

number change

MAWB purge

Edit ULD list

Reload ULD content

Message Center