Local DCS

Departure Control System for medium and small airlines

For those airlines or airport handling agents who wish to have their own Departure Control System (DCS), Travsys can offer an integrated system with our Global Connect solution. In an airport environment the agent probably has connections to several airline mainframe systems. For the check-in agent, the local DCS is just another airline system. The DCS is one of the objects in the CSPNT system.

Possible CSPNT object configuration

The local DCS feature is part of the Travsys Global Connect solution for airport check-in environments. Global Connect enables the connection between the check-in desk and the airline DCS system. If multiple airline systems are available the agent can choose the appropriate connection.

Through one of our customers we can offer an optional graphical user interface (GUI). The GUI can be used to eliminate the differences among the various host DCS systems. The GUI will analyze the host output and display the data at the appropriate field in the GUI. The agent can then easily select the passenger and carry out the whole check-in process using a few key entries or with a mouse. The seat map of the selected flight can easily be displayed in a graphical format in which the various types of seats are displayed in different colors. Click here to see some screen shots. We also have setup a demo server. Contact our sales department for a free demonstation.

For airlines or handling agents who do not have a direct connection to their own centrally installed check-in facility at a particular airport, the local DCS can be utilized. The local DCS will perform all the required functions needed to handle the passenger process. The passenger information (PNL) can be loaded from the reservation system in the most appropriate way for that particular system. The most common way to load the PNL from a scheduled airline reservation system is by downloading it via a data link and store the passenger data into the DCS system. Other methods are also possible and need to be tailored to the particular need at time of system preparation.

For the agent, the local DCS system can be accessed similar than any mainframe based check in system. With the Global Connect solution, the agent can have a window open with several check-in systems at the same time, and switch between those systems by changing to another window.

The local DCS is an option of the Global Connect solution to provide standalone check in functionality. The local DCS system is running on a Windows-NT platform. For a basic system configuration, a Pentium / 166 with 2GB disk space is appropriate.

The picture above gives an example of a possible configuration for a Global Connect solution with the local DCS included. The exact configuration has to be tailored to the local requirements.

The Global Connect solution is using the TCP/IP protocol for communication between the client application at the desk and the communication-, DCS-, and other servers.

The DCS system can be used as a check in system for a single airport as well as for multiple airports at the same time. Depending on the license agreement and the hardware configuration the DCS system can handle several airlines and flights per day. Adding another DCS engine to the Global Connect network can scale the system.

An extensive security matrix is maintained in the DCS system. This matrix will grant the proper right to an individual agent. The elements that can be set for an agent are:

• Agent ID (used for sign on to the system)
• Agent name
• Agent password (used for sign on to the system)
• Carrier(s) the agent is allowed to access
• City code agent is allowed to use
• Agent security level (6 levels).

The system administrator assigns those parameters when an agent record is created or modified. The various security levels determine the authorization rights to the DCS commands. The security level is set according the function of the agent.

The flight handling commands are divided in to two sections:

1. Supervisor commands
2. Agent commands

The supervisor commands are to manage the flight in the DCS system Those commands are like:

• Flight generate
• Flight open
• Flight restrict to set the agent access level for this particular flight
• Flight close
• Flight delete

The agent can perform a status request about a particular flight or to enable or disable auto seating.

With the passenger handling commands all actions can be performed to add or modify a passenger from the list for a particular flight in the DCS system. Usually the passenger details (PNR) are loaded into the DCS system at an earlier stage from the reservation system. If the supervisor has enabled the option, the agent can add passengers to a particular flight at any time. (go shows)

With the check in commands, an agent can perform all required actions to check a passenger in to a particular flight. This can be for individual passengers or for a group of passengers. The seat can be assigned by the DCS system or manually. Seating is based on various parameters. Those parameters are defined by the aircraft configuration, the seating algorithm for this flight, and the passenger parameters. During the check in process the passenger baggage details are recorded and the relevant baggage labels and boarding passes are printed.

If a passenger wants to change his seat, the agent can re assign the seat number and a new boarding pass will be printed.

With the waitlist commands the supervisor and agent can manage any passengers who do not have a confirmed seat available yet. Passengers can be moved onto the waitlist or promoted from the waitlist to the active passenger status. The waitlist can be set to accept a certain number of passengers. This is a parameter for each class on a flight.

With the flight information commands the user can retrieve all information for a particular flight. The information that is available for a flight is:

• display information about all or particular passengers on this flight
• retrieve the no-show list
• show the passengers who are not boarded yet with or without luggage
• display the seat plan
• show the availability per leg for this flight

With the report commands the flight manifest can be generated and the flight closeout report.

Aircraft information

A basic element for a flight is the aircraft information. The aircraft information defines the configuration and the seat plan to be used. The seat plan is generated with an additional application, and the information is stored for each aircraft type and carrier. Besides the physical dimensions of the seat plan, also each parameter for a particular seat is defined. Those parameters can be:

• Smoking or non-smoking
• Priority seat
• Jump seat
• Aisle
• Window
• Emergency exit
• For disabled
• Rear facing
• Unaccompanied minor
• Infant possible
• Special group

Flight information

A flight needs to be generated for each departing city on the route of a flight. A flight can have up to 7 departure cities. With the flight generate command all segments of the flight and the final destination information has to be provided. Elements for generating a flight are:

• Fight number
• Date
• Aircraft type
• Departure city
• Departure date
• Departure time
• Check in time
• City code for origin airport
• City code for destination airport. You can enter up to seven destinations

After the aircraft type is defined and the flight is generated, the passengers can be loaded to the flight. This can be done manually, or with a separate application, which retrieves the PNR information from the reservation system.

Integration with various types of reservation systems can be made.

We have an online demo on the Internet, click here to have a look.

Download the full product description in pdf format: pd-ts-004-01.pdf