www.UTS2000.com    Back    Help contents   Print

Principles of registration in UTS NET 6

The given section is intended for administrators of agencies or airlines

Principles of registration

Registration of SITA USER ID / SITA PASSWORD

Registration of SN-PID

Principles of registration

Registration in UTS NET is carried out by administrators of agencies or airlines (further administrators) is independent

Goals of registration:

• The centralized and safe support assigned to agency SITA USERID / SITA Password

• The centralized, safe and automated updating of SITA Password not less often, than each 120 days. Updating of passwords is carried out only by  administrator. The sales personal (user of UTS Access 6) has no access to passwords and does not know real SITA USER ID / SITA Password

• To forbid to administrators non-authorized using another's SITA USER ID / SITA Password, given to other agencies

• The account of all installed copies of UTS Access program under serial numbers (further SN). Serial number of the UTS Access program is unique identifier fpr each computer in UTS NET network

• The account of all PID's  of GABRIEL system, assigned by airlines to agency

• Binding and linking of everyone PID to a concrete computer in UTS NET network. On each computer with serial number SN can work only registered by the administrator allowed PID

• To forbid to users (sales personal) non-authorized using another's PID, given to other agencies

• To assign additional passwords for everyone SN-PID. The only administrator can assign or cancel the password

• Safe connections of subagents - without granting to subagents real SITA USER ID / SITA Password. Simple support of the biggest subagents networks for main agency.

• Safe using of SITA USER ID / SITA Password in that case, when airlines assign identical SITA USER ID / SITA Password at once to several agencies

• Satisfaction to last requirements SITA on a safety - at a level of data transmission protocols

The system of registration in UTS NET 6 allows for each administrator irrespective of others:

• To support the own table SITA USER ID / SITA Password, received from concrete Airline. Each record in this table is appointed with any unique key KEY. Value of a KEY (a name of a key) unequivocally defines a concrete set: SITA USER ID / SITA Password airlines Airline. This table named as KEY records table. 

• To support the own table SN and PID. For each Serial Number ( SN) define set of PIDs, which can work on a computer with Serial Number SN. This table was named as SN-PID records table. 

• To set KEY value for everyone PID in table SN-PID records. It allows to use PID on a computer with serial number SN and at start PID to use that set: Airline, SITA USER ID / SITA Password which specifies in concrete KEY. Value of a KEY (key name) unequivocally defines a concrete set: Airline, SITA USER ID / SITA Password. 

• To support the table of reserved combinations: Airline, SITA USER ID / SITA Password. This is the set of reserved KEY names.

www.UTS2000.com    Back   Help contents   Section contents

Registration of SITA USER ID / SITA PASSWORD

In SITA network a name of user SITA USERID - unique inside concrete airline. Only one administrator can enter and save into UTS Register a concrete combination: Airline (a code of airline) and SITA USERID in own table KEY records. 

This administrator is the OWNER given SITA USERID.

Owner SITA USER ID can be: 

• Or the administrator of the AGENCY, which have received SITA USERID and SITA PASSWORD at airline 
• Or the administrator of AIRLINE, who supports all registration data for all agents

Owner SITA USER ID

• Edits the data in table KEY records and assign any unique values to KEY names.

• Updates SITA PASSWORD for chosen SITA USERID before password expired. For this purpose there is an automatic procedure of safe password updating.

• Can give out to other agency (SUBAGENT) only PID number and value of key KEY - not informing real SITA USER ID and SITA PASSWORD

• Can enable or disable an opportunity of shared using concrete KEY by other agencies or completely to disconnect a concrete key (but not deleting it)

Work with subagents network

If the main agency has given out to the subagent for work the PID, then administrator of subagency should enter KEY for received PID into table SN-PID records. In each record for everyone PID it is necessary to enter value of the received KEY into field KEY. The administrator of subagency should not add record in table KEY records. It will be impossible.  Administrator of subagency receives from the main agency only KEY name (key value) instead of real SITA USER ID and SITA PASSWORD.

Attention !

Only owners of SITA USERID should insert records in KEY records table. Only they know real SITA USERID / SITA Password for this. If some agency worked as the subagent under another's SITA USER ID (received from the main agency) then subagent should receive from the administrator of the main agency value of KEY (key name) and to enter manually ONLY in records SN-PID records into field KEY for selected PID.

www.UTS2000.com    Back   Help contents   Section contents

Registration of SN-PID

After registration of all Airline codes, SITA USER ID and SITA PASSWORD and assignments of unique KEY value (key name) of each combination, the manager can register allowed combinations of SN-PID in table SN-PID records.

For each allowed combination SN-PID there corresponds one record in table SN-PID records. Record in table SN-PID records can be in two conditions - is enabled for using or is disabled.

Attention! For Each SN-PID record needs to assign KEY to define, under what SITA USER ID and SITA PASSWORD this PID it is necessary to start. 

KEY can be:

• or own KEY  - from own table KEY Records
• or a KEY name, received from other manager
• or reserved KEY name from special set of reserved KEY names

www.UTS2000.com    Back   Help contents   Section contents