System Queue Management

From Wiki Amber.aero
Jump to navigation Jump to search

About System Queues

A queue provides a user with notifications about various events.

An event can be understood as:

  • required user actions to modify the System object;
  • cases when a System object cannot be changed as required.

The recipients of notification of the events are employees of the airline and the provider of the System.

Access to queue management is granted to the user by the administrator according to the role model.

An event or a group of similar events in the System is characterized by the code. Event codes are not editable. Event codes are displayed in notification.

A separate event type is associated with each System object.

Depending on the type of the event, the notification thereof can have a different purpose, as shown in the table. Events of different types are stored in separate queues.

Table - Event types and notification assignment

Event type System object Notification assignment
Events associated with the management of flight resources Flight Airline employees
Events associated with the re-accommodation management Re-accommodation plan
Events associated with the management of passenger booking PNR
Events associated with the manual processing of messages (Reject) Message System provider and airline employees

Access to the queue management is provided for a user by an administrator in accordance with role-based access control.

The queue management presents a control process over arriving notifications and implementation of actions on removing the occurred event.

The basic operations of the queue management consist of:

  • Viewing event reference books
  • Viewing a list of queues
  • Viewing notifications in a selected queue
  • Disabling control over an event
  • Queue modification.

In addition, it is possible to adjust parameters of viewing queues at the level of a user. The personal settings consist of:

  • Using a range of dates
  • Exclusion a queue from viewing
  • Viewing notifications by a selected group of flights
  • Viewing notifications by a PNR type.

An event or a group of single-type events in the System is characterized by a code. Event codes are inaccessible for editing.

  • Event code
  • Reference to an object of the System and an object name
  • Time of forming of event notification
  • Deadline
  • Comment
  • Body of a notification (textual information representation about an object).

An event notification presents a message about the event for a user. The notification has the following parameters:

Event Free sale on the flight is blocked in full or in part. Negative availability in one cabin and more cabins
Heading Flt_Sale_Block Flight ХХ-453 13MAR14 Seg VKO-TJM
Comment Sale on the segment VKO-TJM is blocked due to the application of the “Special space agreement” business rule. Lack of seats for the SSP
Body Flight number, departure date
Deadline Time and date of the event expiration
Notification sending criteria Acceptable limit of the cabin capacity is exceeded. Booking over the allowed capacity, or SSP quota or codeshare block of seats is exceeded the capacity of free seats in the cabin

The example of the notification structure of the event associated with the management of flight resources.

An object name presents brief information about a System object corresponding to the received notification:

The Deadline attribute presents time when a notification loses its relevance and may be deleted automatically.

The Deadline attribute value has the DD.MM.YY HH:ММ:SS format and differs for the events of different types. Typically it is 36 hours from flight departure.

When an event reason is solved and the corresponding flight is not yet departed, the event will be deleted from the following queues before the clearing time:

Queue number Event solution method Queue name
32 Inventory correction NEGATIVE AVAILABILITY
33 Seat addition to SSP SSP ERROR
34 Inventory correction Resource control. CODE SHARE BLOCK_ERROR
35 Inventory correction Resource control. WAIT LIST OVERFLOW
36 Inventory correction Resource control. SSR QUOTA OVERFLOW
38 Seat cancellation SEATS BLOCKED BY OLD EDI-SESS
41 Inventory correction INCORRECT AU
45 Re-acc. plan implementation NO FLIGHTS FOR REACC
46 Re-acc. plan implementation Re-acc control. NON REACC PASSENGERS
47 Re-acc. plan implementation or deletion Re-acc control. REACC BY DEFAULT
50 SSR status update SSR REQUEST_IND PNR
51 SSR status update SSR REQUEST_GROUP PNR
52 Segment status update REQUEST SEATS_IND PNR
54 Segment status update WAIT LIST_IND PNR
55 User notification about possible sync. error for PNR in GDS and Amber.

Auto clearing is performed when the segment is voided and after the deadline. Deadline: 36 hours after the event's segment flight is departed. If there are several such segments in PNR, the Deadline value is set for the flight segment with the latest departure

RestoreSeg
56 SSR VVIP deletion VVIP PASSENGERS
60 Contact data addition PASSENGERS WITHOUT CONTACTS
61 Seat cancellation, ticketing or status update for the wait list or the request EXPIRED MANUAL TIME LIMIT
63 Telegram update and its new processing.

Attention: for the PFS queue, the Deadline value is set according to the Raid storage depth parameter in the Company settings because when the resource is deleted there will be no need for the PFS processing

PFS PROCESS PNR ERROR
64 Connection restoration, first flight segment departure, seat cancellation on the segment PNR BAD CONNECTION
66 Booking confirmation Space control. CODE SHARE GROUP PNR
68 Requests with seat numbers.

Auto clearing condition: specified SSR have status that is not HN (confirmation or rejection) or SSR have the HN status but 36 hours passed from departure of the flight segment for the SSR

Space control. SEAT ASSIGNMENT REQUEST

Queue Parameters

There are queue parameters below:

  • Queue number - A queue number presents a number which contains not more than three figures;
  • name — A queue name presents a text parameter characterizing a type of notifications which are sent to the queue;
  • category:
    • Airlines queue (“Airline”): a queue of events intended for processing by airline employees
    • Provider queue (“Provider”): a queue of events intended for processing by a provider of the System.
  • owner — An owner (Owner) presents a parameter characterizing a group of members which have access to the notification management in a queue.

The following values of the parameters are presented:

    • Airline code: access to the notification management in a queue. Only employees of the specified airline have access.
    • All: access to the notification management in a queue. All users of the System have access.

Depending on who formed a queue and the purpose of this queue, the following queue types are presented:

  • Predefined queues: a set of queues configured by a provider of the System for a user to work, taking into account specifics of his/her activity.
  • Own queues: a set of queues configured by a user.

Predefined queues have a number in the range from 1 to 100, depending on a type.

It is possible to create an own queue based on a predefined queue. In this case, the created queue has the same number as the predefined queue but the Owner field changes into a code of the corresponding carrier on behalf of which the user configured the queue. It is acceptable to assign a number in the range from 101 to 999 inclusive to queues created from scratch.

Important.png For own queues, it is mandatory to specify a code of a member in the Owner field.

A name of a predefined queue and its category are available for editing except for queues of events associated with the manual message processing (the category of the given queue always has the “Provider” value).

Next:

Other sections:

Retrieved from "http://wiki.amber.aero/index.php?title=System_Queue_Management&oldid=4499"