Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION 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
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
  • G06Q50/40—Business processes related to the transportation industry
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION 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/00—Administration; Management
  • G06Q10/02—Reservations, e.g. for tickets, services or events

Definitions

• the present invention relates to a method for loading changes to flight schedules into a computerized air transport reservation system.
• a flight plan describes how the air network is used by planes.
• the schedules are calculated in order to optimize the connections between flights, the use of airplanes and the occupancy of seats.
• the changes to be made to an existing schedule are therefore generally non-isolated changes which have a possible impact on connections with other flight operations.
• the object of the invention is to provide a solution to the problem of flight planning modifications in a computerized air transport reservation system.
• a first advantage of the invention is to deal with a plurality of flight planning changes in a global manner, which makes it possible to envisage reallocations of passenger reservations taking into account all of these changes, whatever the order of changes in the schedule modification file.
• the schedule changes are applied by means of a simulation without final activation, which avoids the risk of disruption of the existing database before complete finalization and validation of the update.
• the invention allows the server to access both the existing database and new records corresponding to the future schedule that should be applied.
• the present invention allows the loading of such changes whatever their nature and also makes it possible to manage a set of parameters for automating the updates to be carried out.
• the present invention relates to a method for loading changes to flight schedules into a computerized air transport reservation system, in which:
• the flight planning database is updated; - the reservations concerned by the flight schedule changes are reassigned for the updating of the reservation inventory database, characterized in that it comprises the following stages: - reception of at least one batch of changes containing flight schedule change data, extraction of individual changes contained in the batch and storage in a register as future planning records - simulation of reassignment of the reservations affected by the schedule changes, by access to the reservation distribution server both to the recordings and to the flight planning database, final updating of the flight planning and reservation inventory databases.
• a graphical user interface is used to check the changes extracted from the change batch.
• a graphical user interface is used for the validation of reservation reallocations.
• SL characteristic suffix
• FSR future planning records
• FIG. 1 schematically illustrates the configuration of different computer means able to be used to implement the invention.
• Figures 2 and 3 are block diagrams of various successive steps of the present invention.
• the method presented here can use an SLS schedule change server able to receive a batch of schedule change tasks to be operated.
• this SLS change server is accessible to a user such as an analyst or a supervisor via a GUI graphical user interface, in particular for checking the changes extracted from the change file constituting the batch of change tasks and for the validation of reservation reallocations.
• a part of the steps of the method of the invention can also be implemented in the distribution part of the reservation system at the level of the distribution server CS and of the existing database db1 comprising the inventory database of the reservations and the flight planning database.
• the level of the SLS schedule change server when a batch of changes arrives, it is possible at first, to check the integrity of the changes and any conflict problems, to test the automation rules and make the data accessible through the GUI graphical user interface.
• the automation criteria relate to the automation of schedule changes and the automation of reservation reallocations.
• the changes can be processed manually or automatically or even present certain manual steps and certain automatic steps.
• analyst speakers proceed to a validation step according to the processing and automation parameters which have been planned.
• FSR future planning records are made accessible by the CS distribution server in the form of a publication.
• each FSR record is assigned a suffix SL which makes it possible to characterize it as a future FSR schedule record in relation to the other data accessible by the distribution server CS,
• the central system and particularly the CS distribution server, is able to access the records of FSR future schedules in order to find the best flight alternatives when booking re-allocations.
• the reservation system automatically chooses a reassignment option (for each change of schedule requiring it). This option is chosen from the FSR future schedules or the current schedules (for flights not affected by the current batch).
• the system checks them using the reassignment automation rules. Reallocations not satisfying these rules are subject to validation by an operator (who can then modify the options calculated automatically by the system).
• the planning database is first updated.
• the system then allocates a unique “I” operation identifier characterizing the current batch.
• the reservation system then receives all of the reassignment instructions as well as the operation identifier “I”. He must then guarantee the uniqueness of modification of each reservation in the context of operation "I”.
• a preferred embodiment of this constraint consists, for each modification of a reservation, of: - checking that this reservation does not have the "I" mark, in this case modifying the reservation then marking the modified reservation with the identifier "I". As reassignments are made, the inventory database is also updated. The three databases (inventory, reservation and planning) are then up to date and the FSR records can be deleted.
• SLS schedule change server
• CS db1 distribution server: existing database
• GUI graphical user interface

Landscapes

• Business, Economics & Management (AREA)
• Tourism & Hospitality (AREA)
• Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Economics (AREA)
• Human Resources & Organizations (AREA)
• Marketing (AREA)
• General Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• Strategic Management (AREA)
• Entrepreneurship & Innovation (AREA)
• Quality & Reliability (AREA)
• Operations Research (AREA)
• Development Economics (AREA)
• Health & Medical Sciences (AREA)
• General Health & Medical Sciences (AREA)
• Primary Health Care (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Applications Claiming Priority (5)

Publications (1)

Family

ID=29738031

Family Applications (1)

Country Status (9)

Families Citing this family (11)

Citations (2)

Family Cites Families (9)

• 2003
  • 2003-06-13 EP EP03760062A patent/EP1552446A1/de not_active Ceased
  • 2003-06-13 CA CA2488194A patent/CA2488194C/fr not_active Expired - Lifetime
  • 2003-06-13 BR BR0311873-8A patent/BR0311873A/pt not_active Application Discontinuation
  • 2003-06-13 US US10/518,515 patent/US8069069B2/en active Active
  • 2003-06-13 JP JP2004513976A patent/JP2005530243A/ja active Pending
  • 2003-06-13 AU AU2003255699A patent/AU2003255699B2/en not_active Expired
  • 2003-06-13 WO PCT/FR2003/050008 patent/WO2003107229A1/fr active Application Filing
  • 2003-06-13 CN CN038142279A patent/CN1662915A/zh active Pending
• 2004
  • 2004-12-15 ZA ZA2004/10128A patent/ZA200410128B/en unknown

Patent Citations (2)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events