tina_manual_en_24.01.2011

8/21/2019 TINA_manual_EN_24.01.2011

1/309

Travel IntraNet Application

Handbook

8/21/2019 TINA_manual_EN_24.01.2011

2/309

TINA Handbook

Contents

CONTENTS............................................................................................................................ 2

1. ABOUT THIS GUIDE..........................................................................................................2

2. TINA PRESENTATION.......................................................................................................4

3. HOME MODULE............................................................................................................ 17

4. THE CLIENTS MODULE............................................................................................... 23

5. THE SUPPLIERS MODULE..........................................................................................47

6. THE RESERVATIONS MODULE.................................................................................. 63

7. THE INVOICES MODULE...........................................................................................151

8. THE AMADEUS MODULE..........................................................................................176

9. THE SA MODULE .................................................................................................... 2!1

1!. THE TOOLS MODULE .............................................................................................2!9

11. THE DOCUMENTS MODULE...................................................................................218

12. THE ADMIN MODULE..............................................................................................231

13. THE REPORTS MODULE.........................................................................................292

14. GLOSSAR" O TERMS............................................................................................... 3!2

15. OPERATION #OR$LO# SUGGESTIONS...............................................................3!4

16. ANNE%.......................................................................................................................... 3!9

1. About this guide

1.1. Its target

This guide is meant to present the TINA Application software in detail and the operations that

it can support. It represents an information source for new Users who wish to familiarize with

the program but also for advanced Users who wish to renew certain details or to stud less

known options.

This guide is a real help for all TINA Users both novice and advanced and it serves as first

help in solving issues and troubleshooting.

!ersion ".#$.#.#%&' (age " of $&%

8/21/2019 TINA_manual_EN_24.01.2011

3/309

TINA Handbook

1.2. Guide structure

As the Application is divided into several modules in order to separate the operations and

tasks) the guide will follow the same modular architecture for Application description. *ver

module will have its sub+modules) sections and subsections) zones for icons and operations.

The guide is divided into ' main chapters,

#. About this guide a few introducing words about the guide itself) structure and

conventions

". TINA introduction Application presentation) market share) necessit and advantages

$. Application description it is divided into chapters for presenting ever separate

module

'. -reuent asked uestions and troubleshooting separate chapter for most freuentl

asked uestions and complete answers for them and also troubleshooting and problem

solving for most popular issues

1.3. General sybols! conventions and ters

Inside this manual are a set of notations) smbols) conventions and terms that are to be

presented in this chapter.

1.3.1. "#epli$ication

In order to consolidate the e/planations and the theor in this guide) there have been

inserted several e/amples from common practice. 0here necessar) below the paragraph

has been inserted the formula,

*/ample

followed b the e/ample itself) usuall together with a print screen form the Application

describing a true situation.

1.3.2. %arning

0here there is ver important information has been used the formula,

This information is ver important and reuires special attention.

1.3.3. In$oration

-or helpful information regarding the respective area) it has been used the formula,

Helpful information

!ersion ".#$.#.#%&' (age $ of $&%

8/21/2019 TINA_manual_EN_24.01.2011

4/309

TINA Handbook

2. TINA presentation

2.1. Introduction

2.1.1. Actual conte#t and necessity

The sustained evolution of travel 1ervices around the 2lobe gave birth to the necessit of

integrating informational sstems to manage all the operations.

If on one side) the airline companies started this integration in earl times and now are

distributed b enormous informational sstems) sustained with high financial efforts) on the

other end of the travel chain the Travel Agencies must deal with huge amounts of data and

operations. 1olutions were reuired to help Travel Agencies to organize) manage and control

their activit faster and more reliable.

TINA 3Travel IntraNet Application4 is an *5( 3*nterprise 5esource (lanning4 which was

developed to overcome this problem offering a unitar sstem to all departments from a

Travel Agenc to work with. A uniue database and operational resources are shared across

the network between all operational cores of the Travel Agenc to organize and optimize the

working process.

*ven if the new sstem ma look difficult to operate at the beginning) with proper training

and after a while of sustained operation) the Application proves to be ver intuitive and

helpful.

0hile the agents are migrating to a modern) more organized wa to work) the manager finds

useful reporting tools) ver important for coordinating) and short term and long term

predictions.

2.1.2. &asic principles

The *5( for travel activities in a Travel Agenc is compliant with some basic statements,

The Application has been created to help the agents and the manager) b organizing

their activit for faster operation and greater efficienc.

In order to be used b the agents) a sstem must be comfortable to operate. 6eing

developed together with e/perienced Agenc managers and agents) the User interface

has been carefull studied and modelled to adapt as much as possible to agents needs

for faster operation) offering toda a mature solution) read to solve the most various

situations found in Travel Agencies these das.

The Application is intuitive and follows a natural and logical workflow.

TINA is web based software which runs on a central server and allows man agents

spread around Agencies operational cores) whether the are in the same building or in

different countries to reuest its 1ervices for fulfilling their tasks. *ach User logs into the

sstem based on a Username and password and accesses the resources that the

1stem Administrator allows him to. This ensures sstem securit and scalabilit.

The sstem uses the latest programming technologies and the internet 7 8AN network to

transfer data. This ensures high performance and reliabilit with minimal implementation

cost.

!ersion ".#$.#.#%&' (age ' of $&%

8/21/2019 TINA_manual_EN_24.01.2011

5/309

TINA Handbook

The developers together with their partners offer e/tensive Application support) b phone

or b e+mail) solving basicall an kind of problem as soon as possible. Nor agents or

managers will ever be in the situation of not having a reliable source of support.

The sstem is profitable) considering the efficienc growth 7 cost ratio. In a little while

after the implementation the efficienc parameters start to go up) proving that the

investment was a success.

2.2. 'yste $unctions

9anagement of suppliers and their 1ervices and the Agenc :lients. The are recorded

and stored in the database for future searches and reports;

Integrates all functions and features for a 5eservation operation) from

8/21/2019 TINA_manual_EN_24.01.2011

6/309

TINA Handbook

2.(. General coon details

0hile this paragraph there will be presented the common details used for Application

description. There will be a general description for buttons and smbols tpes and

categories) filed tpes and common language.

Although visual aspect of smbols inside the Application it is preserved and the same looking

smbol has the same basic meaning in all instances) special features that are different for

each situation will be presented in their corresponding section of the guide.

2.(.1. 'election and navigation through the enus

In the graphical Users interface there is a header in blue color showing the current module

and sub+module in the right side. 6elow this header there is the main menu which allows the

selection of the module the User wishes to work in 3:lients) 1uppliers) 5eservations)

Invoices) A9A>*U1) etc.4

-ig. Interface menus

5ight below the main menu there is the secondar menu with sub+modules belonging to

each module from the main menu.

Navigation and selection through the modules and sub+modules is being made b clicking

with the mouse on the corresponding button or on the te/t in the web page.

This wa of navigation is common to Internet web pages and it is available in all Applicationinstances.

*/ample

In the upper picture the C5eservations listD sub+module belonging to C5eservationsD module

is selected.D

The secondary menu with sub-modules appears while mouse hovering over each module from

the main menu allowing the jump directly into another sub-module without selecting its parent module

first. After a short time, the secondary menu changes back to the one corresponding to the currently

selected module.

2.(.2. )sed icons

!isuall intuitive icons with basicall the same meaning have been used in all Application

instances.

2..2.!. "nformative icons

+ indicates that additional information is available in that area. It usuall gives tips

about program and option usage but also information about that particularl record.

1imple mouse hovering over the smbol will relive e/tra information and useful tips for

operator assistance.

!ersion ".#$.#.#%&' (age E of $&%

8/21/2019 TINA_manual_EN_24.01.2011

7/309

TINA Handbook

+ opens a window with the description for a certain element. These details are alwas

available for the operator b this uick access button allowing fast consulting without

going to the section where the element has been previousl defined.

*/ample

-or C1uppliersD module) pressing the smbol corresponding to one 1upplier implies the

opening of a window like the one below containing all the information for that 1upplier. The

window will close b pressing the F/G button in the upper right corner.

-ig. >etail window

+ red arrow placed in front of a form field marks it as mandator. Inputting the right

data in that field is compulsor for the validation of the form.

*/ample

In the :orporation75eseller adding form below the CTpeD) C:ompanD and CAliasD fields are

mandator. 5ight data must be selected or inputted before the adding process can be

completed.

-ig. 9andator fields

+ present in the right side of a field) marks it as an autosearch field. -or

details about autosearch fields see chapter, ".'.$

!ersion ".#$.#.#%&' (age of $&%

8/21/2019 TINA_manual_EN_24.01.2011

8/309

TINA Handbook

+ indicates the presence of a date field. (ressing it will cause the opening of a

calendar window from which the User can select the desired da) month or 7and ear.

-ig. :alendar window

2..2.2. #perational icons

+ blocks the corresponding element in making it unavailable for future use7processing

inside the Application

*/ample

0hen a 1upplier is blocked) his name and his 1ervices will not be available in the offering

process. It remains in the database and in the list but it cannot be used.

+ unblocks a blocked element in making it available once again inside the Application

+ opens a uick action menu right ne/t to the corresponding element with special

options for it) especiall shortcuts to actions

*/ample

-or clients listing in C:lientsD module) the special options smbol opens a menu like the one

below with uick access to (assenger adding for the corresponding :ompan and7 or

(assenger listing for the corresponding :ompan.

-ig. 1pecial options

+ refers to :ontact (ersons) for e/ample a :ompans :ontact (ersons

+ edits the corresponding element b opening a form that allows changing the

element data or adding new information in the blank fields

+ deletes the corresponding element.

$or %ervice the symbol refers to effective deletion from the database but for an invoice, the

symbol voids the document.

2.(.3. Autosearch $ields

These fields constrain the data input. The data that the User can input here must be present

in the database. If not) the element must be first introduced in the database and after that

reinserted in the autosearch field.

!ersion ".#$.#.#%&' (age J of $&%

8/21/2019 TINA_manual_EN_24.01.2011

9/309

TINA Handbook

0hen writing data in such a field) the corresponding section of the database is automaticall

browsed according to inputted characters and a list with possible choices opens below. To

validate the input) the User must select from the list the desired element.

These fields are marked b the dotted blue arrow in the right side.

*/ample

In order to write the destination countr for a trip) the User cannot insert a countr that is not

present in the database.

The list of &ountries and &ities database contains all major travel locations. However, new

elements can be manually added.

To input the countr) the User starts writing the name of the countr in the autosearch field

and a list with possible choices from the countries K cities area in the database opens below.

The desired record can be selected with the mouse or F*nterG and this wa the data is

validated.

-ig. Autosearch field

$ewer letters introduced return more results' more letters restrain the search showing fewer

precise results.

1o) to input C2ermanD the User starts writing CgerD and a list with C2eraC 3from 2erman4)

C2ermanD) C2ermistonD 3from 1outh Africa4 and CNueva 2eronaD 3from :uba4 choices opens

below.

The User can stop now and select with the mouse or F*nterG the desired countr or can

continue writing to obtain fewer but more precise results.

-or multiple results) the total number is shown at the bottom of the open list. This list can be

browsed using the CFFD and CGGD buttons to reach to the desired countr.

If no result can be found according to written characters) the search will return Cno resultD

message and the input cannot be finalized. The User must first introduce the new element in the

database and then come back to restart the writing and searching process.

"nserting only one space or double clicking with the mouse or pressing (enter) inside such a

field, it can be used as a selector, showing all the available elements.

!ersion ".#$.#.#%&' (age % of $&%

8/21/2019 TINA_manual_EN_24.01.2011

10/309

TINA Handbook

2.(.(. *ate $ields

0henever time date is necessar as input) the User writes the date in a dedicated field tpe)

named Cdate fieldD.

The Application speeds date insertion process b accepting a variet of date formats,

da can be written both in # and " digits format

month can be written both in " and # digits format and also in letters 3nov) un) an) etc.4

ear can be written both in ' and " digits format

These $ parameters can be separated b more tpes of characters, comma) dot) space)

slash) minus) etc4

The >AL +G 9

8/21/2019 TINA_manual_EN_24.01.2011

11/309

TINA Handbook

-ig. :alendar window

2.(.+. Tooltips

Tooltips appear in information windows that popup while mouse hovering over different tools

and close after mouse passing. These windows contain useful information regarding the

respective tool functionalit. The operator can see the tool description at an time therefore

he7she does not have to memorize it.

2.(.,. -ilter and sorting

9an sections in the Application include lists of elements 3:lients list) 1uppliers list)

5eservations list) invoices list) etc4. As the number of elements in a list can be ver large) a

wa of filtering) searching or sorting has been developed for each tpe of list in order to show

onl the reuired elements at a time.

In the upper side of each such list is a filtering button. 6 clicking on it) a filtering menu

opens with more or less filtering criteria concerning the respective list of elements.

After proper filters setup) the User selects FAppl filtersG and the in the list appear onl the

desired elements. (ressing the first filtering button again) the filters menu closes.

#nce set, the filters stay unchanged during operation even if the filter menu closes. The shown

list remains the same, according to last selected criteria. "f the *ser wants the whole list again or other

elements listed, he+she must reopen the filter menu and reset the filters.

*/ample

Here is an e/ample of a comple/ filters menu) from 5eservations list.

-ig. 5eservations list filtering menu

The F5eset filtersG button can be accessed to reset the filters into default setup.

The search result will depend simultaneousl upon all the selected criteria. All shown results

compl with the selected criteria in the sorting area.

!ersion ".#$.#.#%&' (age ## of $&%

8/21/2019 TINA_manual_EN_24.01.2011

12/309

TINA Handbook

Although the criteria for each type of list may be different, the filtering concept and usage

remains the same.

2.(.. 'election and navigation through lists

1election inside the lists is being done with mouse clicks directl on the element and

navigation through lists pages b using the page selection menu in the bottom.

The User can browse page b page using the two buttons from the left side of page selection

menu or can directl select the page number from the pages selector. The User can also

select the number of elements to show at a time in the list.

-ig. (age selection menu

-rom the above figure) the list it corresponds to shows elements from # to #& from a total of$&B. The number of the current page is # and the number of elements shown at a time is set

to #&.

2.(./. Adding in$oration record

-or certain modifications of elements in the database 3adding) editing) etc4 the Application

records the User that made the modification and the time of the modification. This data is

saved for future verifications.

The details are shown in a separate column) for ever element in the list.

*/ample

In the figure below it is shown a simplified Users list.

-ig. Adding record information

In this e/ample) the last column shows the date the User was added. If the smbol is

accessed) supplementar data is shown) including the User who made the record) from

which epartment.

2.(.0. )sers classes and access levels! accessible odules and subodules

2...!. *sers classes

Users identifing to the Application based on an account with Username and a password can

be classified in different categories,

2...!.!. ormal *ser

It is the class of Users that includes Agenc emploees from different departments which

need access to different modules and sub+modules to accomplish their tasks) like tourism

operations) 5eservations) billing) accounting) etc.

2...!.2. Advanced *ser

!ersion ".#$.#.#%&' (age #" of $&%

8/21/2019 TINA_manual_EN_24.01.2011

13/309

TINA Handbook

Users from this class are from management areas with higher access rights and

administrative responsibilities. This User can make certain configurations and settings) can

e/tract reports) etc) according to :ompan polic.

2...!.. Application Administrator

He is the person in the Agenc staff that has full access rights to all Application modules.The Administrator usuall can do an maintenance operation) configurations and settings for

Users) 1ervices) profiles) rules and protocols in correspondence with Agenc polic.

He is the right person to contact in case of any problems, configurations, permissions,

definitions, settings, etc.

2...!.. %upport *ser

This User is not part of the agenc staff. It is a Technical 1upport Assistant for TINA with full

access rights to the Application modules. He can help in special cases) when the Application

Administrator cannot solve the problem. Although this support User has full accessprivileges) his access rights are legall limited to data reading onl for assisting the operator

through its path. He cannot interfere with effective operation.

It is recommended to contact the Technical 1upport for TINA onl after first consulting this guide

and second after consulting with the Application Administrator.

2...2. Access levels

>epending on his function) tasks) department) office) an user can have different access

rights for operating inside the Application modules. The Application Administrator will set

permissions for each User according to Agenc polic.

6ased on access level an User will be able to see onl the modules and sub+modules useful

during his duties and tasks inside the Agenc.

*/ample

A front desk Agent ma have access onl to the C:lientsD) C1uppliersD) C5eservationsD

CInvoicesD and CToolsD modules) to fulfill hes tasks within the Travel Agenc. In order to

make the operation as simple as possible for the respective Agent) the Application

Administrator will make available for him onl the above mentioned modules.

2.(.1. *ocuents handling

9ost of the documents that are usuall needed for travel operations 3voucher) offer to client)

invoice) anne/) receipt) etc.4 can be issued directl from the Application. 9an of the

reuired fields are automaticall inserted b the Application and others are User defined)

placing the document issuance a few clicks awa.

>ocuments are met in the C5eservations listD and in the C:lients invoicesD sub+modules and

can have $ sources that can generate documents,

The 1ervice

The 5eservation

The invoice

!ersion ".#$.#.#%&' (age #$ of $&%

8/21/2019 TINA_manual_EN_24.01.2011

14/309

TINA Handbook

The documents are handled unitar b the Application. However each source has a standard set

of possible documents and onl those can be issued within the corresponding section. New document

tpes can be added

The 1ervice 3accessed from the C5eservations listD sub+module4

voucher

offer to client

offer from supplier

etc.

The 5eservation 3accessed from the C5eservations listD sub+module4

cumulated client offer

travel contract

etc.

The invoice 3accessed from the C:lients invoicesD sub+module4

invoice

balance

anne/

receipt

pament order

minute of refund

pament reuest

promissor note

check

etc.

The Application has a powerful documents templates design tool that allows documents setupfrom the Application graphical *ser interface. This way, the documents layouts, fields, logos and

aspect are set by the Application Administrator from the /0ocuments1 module.

The documents parameters) fields) behavior and templates are defined b the Application

Administrator

2..!.!. 0ocument issuance steps

Accessing the smbol from an of those sections) a new window opens and allows the

User to issue a document b going through $ steps,

1tep#, select document tpe

1tep", select a document template for earl selected document tpe

!ersion ".#$.#.#%&' (age #' of $&%

8/21/2019 TINA_manual_EN_24.01.2011

15/309

TINA Handbook

1tep$, complete the necessar fields if an) select document series and finall press the

F2enerate documentG button

*/ample

In the e/ample below) an invoice needs to be generated. 0hen accessing the smbol

from the C:lients invoicesD sub+module) from an invoice that has not been issued et and

therefore no document has been generated for it) a generation form opens allowing the User

to select what kind of document he7she wants 3in our case CIN!- format has been selected4

If other fields would have reuired User intervention for the current document 3data not

present in the database but mandator in the document or simpl optionall editable b

User4 the would have appeared in the C:onfirm data72enerate documentD area. These

fields ma reuire mandator or optional input or ma ust show their info.

1ome fields ma be mandator to the current document but cannot be simpl inputted in thisform. The Application warns the User to go back in the reuired sections and add correct data where

necessar. After that) the User can return to finalize document generation.

In case of man series for a document tpe) the User can also select the series. 3In our case

the series field is C50UD is alread selected and the number the document will have is E4

-ig. Invoice generation form

%ome steps may be jumped due to templates setup, default settings for them, number of

templates, document types, etc. $or details about document templates and setup please contact the

Application Administrator.

After proper selections and data input) the User should press the F2enerate documentG

button and the document is generated and saved inside the Application.

To select other document tpe or other template) the buttons Fselect other tpeG and Fselect

other templateG respectivel can be accessed and go back to previous steps.

-or process abortion) the button F:ancel document generationG can be accessed.

To further handle the document) press the F(reviewG) F>ownloadG)F(rintG or F*+mailG

buttons. >epending on the template output format 3(>-) HT98) 5T-) etc4 and handling

software 3for e/ample AdobeO 5eaderO for (>- documents4 it can be sent b e+mail) stored

on personal workstation or printed on paper.

!ersion ".#$.#.#%&' (age #B of $&%

8/21/2019 TINA_manual_EN_24.01.2011

16/309

TINA Handbook

1ome documents formats ma reuire third part free handling software. -or e/ample (>-

format documents can be opened b AdobeO 5eaderO software

-ig. 1tored documents management

0hen accessing again the smbol) it will open the same form allowing new document

generations. This form has an e/tra section that allows earlier generated documents

management. The document generations can be selected from the selector) downloaded)

printed) viewed or interrogated for details.

2..!.2. 0ocuments numbering

The Application manages the documents numbers. -or each document tpe) one or more

series can be defined with numbering intervals.

*ver time a document is issued) it gets the ne/t number in the selected series making it

uniue b content.

%eries are defined by the Application Administrator in the /0ocuments1 module. $or details

about document series contact the Application Administrator or see chapter3 !!.!.

If no series has been defined and made active for a document tpe) the User is warned when is

tring to generate the document and the issuance cannot be completed. Therefore at least one series

must be defined and activated first for that tpe of document.

2..!.. 0ocuments issuance sensitive details

8/21/2019 TINA_manual_EN_24.01.2011

17/309

TINA Handbook

>ocument issuance and document printout are two different terms and must not be confused. A

document must first be issued. The printout can be optional. -or e/ample) an invoice can be simpl

sent b e+mail to the :lient and never printed on paper

3. H45"6 odule

This is the first module in TINA that offers to the user a short overview of his pending tasks.

The module offers an intuitive framework for the Agent and guides him to fulfil his tasks in an

eas wa) according to the shortcuts that are available.

This module permits an e/tensive setup from the User interface in order to adapt the

Application to the Agent needs

3.1. 'tatistics6 section

In the left side of the CHomeD page) statics of the user authentication are displaed)

according the user logged in. The user has the possibilit to view the time and date of his

current authentication) the time and date of his last authentication and the total number of his

authentication since his first authentication in the sstem.

3.2. TINA links6 section

This section displas that are most accessed b the user. In this section the user has thepossibilit to select the links that he uses the most.

!ersion ".#$.#.#%&' (age # of $&%

8/21/2019 TINA_manual_EN_24.01.2011

18/309

TINA Handbook

The option allows the user to configure the links) practicall to select the links that he

want to have in the list. The links order can be rearranged b selecting and moving them)

dragging with the mouse.

3.3. 7ersonal links6 section

The user has the possibilit to define other links) different from the TINA links) which will help

him in his activit

3.(. 4perational details6 sectionThis section offers the user the possibilit to view the operational details for the current

reservation. -rom this section he can also access the P5eservation detailsD module and the

PQuick navigationD module

!ersion ".#$.#.#%&' (age #J of $&%

8/21/2019 TINA_manual_EN_24.01.2011

19/309

TINA Handbook

3.+. General details6 section

This section offers the user the possibilit to view the last reservations on which the user

worked on) the last invoices that he added and the tickets that he did not processed from

Amadeus

3.,. Calendar6 section

This section gives the possibilit to the user to view the tasks and the events for the current

da or for the current month.

3.. )pdate application

This section gives the user the possibilit to automaticall update the sstem. The update

can be performed onl if a new version is available for the installation. The update is divided

in four stages which suppose, verifing if there is a new version) downloading it) unzipping it

and the actual update as it can be seen in the image below,

!ersion ".#$.#.#%&' (age #% of $&%

8/21/2019 TINA_manual_EN_24.01.2011

20/309

TINA Handbook

The four steps that the user needs to follow are,

:heck the new version

The user has to press the check ne8 versionbutton in order to verif if a new version is

available for the update. If a new version is available a confirmation message will appear

and the second step will become available) as it can be seen in the image below,

If no new version is available the user cannot proceed to the second step) as it can be

seen in the image below,

>ownload new version

The user has to press the do8nloadbutton in order to download the new version of the

application) as it can be seen in the image below,

!ersion ".#$.#.#%&' (age "& of $&%

8/21/2019 TINA_manual_EN_24.01.2011

21/309

TINA Handbook

The download of the new version may take a few minutes, it depends on the bandwidthbetween the T"A server and versions server.

Unzip new version

The user has to press the unpack updater button in order to prepare the files for the last

step +G update version) as it can be seen in the image below,

"n order for the un4ipping to be successfully performed, the T"A server must have the 5un4ip6

command installed. "f not, the update cannot be performed and the system administrator must be

contacted to solve the problem.

Update version

!ersion ".#$.#.#%&' (age "# of $&%

8/21/2019 TINA_manual_EN_24.01.2011

22/309

TINA Handbook

The user has to press the update versionbutton in order to perform the actual update

of the application. It is ver important that before starting the e/ecution of the last step

3Rupdate version4 to take into account that the application will be completel blocked 3no

user will be able to work in TINA4. 0e recommend performing the updates in the evening

or during the weekends) when no user is active in the application.

After pressing the start updatebutton) a new pop+up window will open) in which the

user will has to press the Click hereas it can be seen in the image below,

After the update is successfull performed) the TINA 8icense must be renewed.

"f from any reason, the update cannot be successfully performed, the application will remainblocked until solving the problem. "n this case the 0&s7 technical team has to complete manually the

update 8 during this period the application will be blocked. "f the problem mentioned above appear,

!ersion ".#$.#.#%&' (age "" of $&%

8/21/2019 TINA_manual_EN_24.01.2011

23/309

TINA Handbook

please contact the T"A %upport T9A: by e-mail tinasupport;dcsplus.netor by phone

72!.2.!.2.

(. The Clients6 odule

This module manages the Travel Agencs :lients.

:lients are divided into two classes with their sub+classes,

8egal *ntities 3:ompanies4

:orporations

5esellers

Individuals

:ustomers that come from a :orporation or a 5eseller or Individual :ustomers who are

consumers of travel 1ervices are called (assengers.

:orporations75esellers and :ustomers are treated separatel) each in a sub+module.

:orporations sub+module lists and manages the :orporations and 5esellers

:ustomers lists and manages the :ustomers

(.1. Corporations6 subodule

The Agencs :ustomers7:lients can be either from a :orporation or 5eseller or can be

individuals. 6oth :orporations and 5esellers are :ompanies. The :ustomers7:lients who are


:orporations and 5esellers are listed together in the :orporations administration page.

:orporations, the legal entities that reuire travel 1ervices for their (assengers.

5esellers, legal entities that resell the Agenc travel 1ervices.

(.1.1. 5ain page description

9ain page named P:orporations administrationD

It shows the list of the Travel Agenc :lient :orporations. *ach :orporation that the Agenc

serves must be recorded into the database along with its details. All records are saved for

travel operations) future reports and Travel Agenc log.

The list can be searched and filtered for showing onl those :orporations that correspond to

desired criteria.

!ersion ".#$.#.#%&' (age "$ of $&%
mailto:[email protected]:[email protected]

8/21/2019 TINA_manual_EN_24.01.2011

24/309

TINA Handbook

-ig. The :orporations administration page

The :orporations75esellers can be sorted according to different criteria 3alias) client tpe)

trust) adding date) or :ompan name4

Above the list there is a tab that opens the filter menu named C:orporations75esellers filtersD

and in the right side there is a button named FAdd :orporation75esellerG used to add newelements.

The column heads colored with blue can be clicked to sort the list by that column. The sort can

be ascending on descending with every click on the column head.

(.1.2. 4ptions $or Corporations9:esellers

-ig.

8/21/2019 TINA_manual_EN_24.01.2011

25/309

TINA Handbook

+ opens the edit menu for the corresponding :orporation75eseller. It opens a window

which allows :orporation75eseller data change. -or details about how to edit a

:orporation75eseller see chapter, '.#.B

+ deletes the corresponding :orporation75eseller

A :orporation75eseller can be deleted onl if it has not been present into a travel action.

(.1.3. -iltering and searching in the Corporations9:esellers list

In order to show onl the desired :orporations75esellers from the whole list) the User will

adust the filters according to different criteria.




-ig. :orporations75esellers filters menu

-iltering can be made based upon ' criteria categories,

:ompan tpe, shows onl the :orporations or 5esellers) depending on the selector

=e account, the 9anager7=e account 7 5esponsible User for that :ompan shall be

entered in order to filter b him7her

:ompan added b, shows onl those :ompanies added in the database b the User

inserted here

Trust, shows onl the :orporations or 5esellers that are associated with a certain trust

Te/t filter, the User inserts the first word or a part of the first word from, the client alias)

the compan name or a number or beginning of a number from financial data or

compan internal id) in order to filter those elements that compl with these inputs and

after that the user selects the wa to search in the field

(.1.(. Adding a ne8 Corporation9:eseller

The adding process can be made here or in any other instance when needed during effective

operation.

8/21/2019 TINA_manual_EN_24.01.2011

26/309

TINA Handbook

section. A new window opens containing a form where the User can input relevant data

about the new :orporation75eseller.

-ig. New :orporation75eseller adding form

1ome fields ma be different from the ones in the shown e/ample

:ompan, the complete official name of the :lients :ompan. In front and after this

name the User can choose the tpe of :ompan and fiscal terminolog if applicable. In

case of not knowing these e/tra details) the User will select the blanks for prefi/ andsuffi/ of the name.

*/ample, 1: 1I*9*N1 5

8/21/2019 TINA_manual_EN_24.01.2011

27/309

TINA Handbook

-inancial data, information about financial registration

(hone) fa/) e+mail) website, 1ome of the compan contact data

:ontract, in case the :ompan has a contract with the Travel Agenc the User can

select CesD

:omments, other data concerning the :ompan

The fields marked with red are mandatory. The others are optional and for faster operation they

can be left blank. However some of these optional fields may be re=uired for future operations.

8/21/2019 TINA_manual_EN_24.01.2011

28/309

TINA Handbook

(ament options, forms of pament the :ompan can pa the invoices issued for this

8/21/2019 TINA_manual_EN_24.01.2011

29/309

TINA Handbook

1i/ sections are available in the :ompan profile menu) selectable b the upper tabs,

(ricing polic for that :ompan

:orporation segment for that :ompan

Invoices preferences for that :ompan

9anagers definition for that :ompan

:ontracts for that :ompan

1pecial dates for that :ompan

.!.?.!. %ervice fee @ discount

The C1ervice fee K discountD section allows the User to predefine a pricing polic that the

Travel Agenc has settled with the corresponding :ompan) for each 1ervice) for each

calculation mode.

-or each e/istent criterion) the fields below are completed with the proper values 3positive or

negative4. 0hen adding an offer for a service with a defined service fee7discount scheme)

the grid is browsed and the algebraic sum of each criterion is calculated. >epending on each

service fee calculation method) is the sum of the gross valued or limited to a ma/imum value

3if the amount e/ceeds the ma/imum value defined4 and appl this result as service fee for

the new offer.

!ersion ".#$.#.#%&' (age "% of $&%

8/21/2019 TINA_manual_EN_24.01.2011

30/309

TINA Handbook

The ticketing service is treated in a special wa) meaning that the service has more criteria

than other service as it can be seen in the image below,

This information input can optimi4e the overall process because the *ser does no longer have

to insert it each time in the offering stage. All data entered here can be modified in the offering

process.

In the above picture there are $ geographical areas, >omestic) *urope and Intercontinental

corresponding to different financial policies. These areas are worldwide available.

!ersion ".#$.#.#%&' (age $& of $&%

8/21/2019 TINA_manual_EN_24.01.2011

31/309

TINA Handbook

.!.?.2. &orporation segment

The C:orporation segmentationD allows the User to associate the :ompan to a segment

from a predefined list. -or details about segmentation section see chapter, %.'

-ig. :ompan profile corporation segment

.!.?.. "nvoice preferences

The CInvoice preferencesD section allows the User to predefine a rule for calculating the due

date on invoices issued for the corresponding :ompan) select a scheme for the invoices

rows description and also select the default document template for each document tpe

available on the invoice pivot.

-ig :ompan profile invoices preferences

There are $ was of defining the due date,

calculating it b adding a defined number of das from the invoice issuance date

defining one or more month das in which the :ompan can e/ecute paments

without profile) in this case the general due date will be applied

!ersion ".#$.#.#%&' (age $# of $&%

8/21/2019 TINA_manual_EN_24.01.2011

32/309

TINA Handbook

The Application will automaticall input the calculated due date in the invoice.

This information input can optimi4e the overall process because the *ser does not longer have

to insert it each time in the invoice form. All data entered here can be modified in the invoice

generation process.

The :lients default templates option allows the User to select a default template for each

document tpe related to a certain corporation. 0hen the User issues an invoice related to a

corporation that has a default template previousl set) the application will automaticall set

as default that template.

"n order to issue invoices using a template previously defined, the user must have access to that

template. The access is set from 0ocuments module, 0ocuments templates section -) *sers access.

$or more details see chapter !!.2

.!.?.. :anagers

The Application allows definition of responsible Users for each level of :ompan structure,

-or :ompan overall

-or each :ompan

8/21/2019 TINA_manual_EN_24.01.2011

33/309

TINA Handbook

-ig. :ompan profile contracts

-or each added contract) the User has the possibilit to add the e/pir date of the contract.

-or this option to work a cronob must be added and configured. -or more details see

chapter,#".B.#

.!.?.?. %pecial dates

The application allows the User to enter some special events related to the selected

:ompan.

-ig. :ompan profile special dates

(.1.. Contact 7ersons adinistration

The Application allows recording of man :ontact (ersons for one :orporation75eseller.

8/21/2019 TINA_manual_EN_24.01.2011

34/309

TINA Handbook


can be left blank.

After data insertion the User should press the FAddG button to finish the operation. (ressing

F*scapeG from the keboard or the F:ancelG button from the window cancels the process

and closes the add window.

After successful adding) the new :ontact (erson shall appear in the :ontact (ersons list.

The successfully adding operation will be announced by a message. Any error in field input will

be detected by the Application. The adding process will only be possible after necessary corrections

A few options are available for :ontact (ersons 3 ) ) 4 with same meanings as

everwhere else in the Application, show details) edit :ontact (erson data) delete :ontact

(erson respectivel.

(.1./. 4$$ices adinistration

The Application allows recording of man

8/21/2019 TINA_manual_EN_24.01.2011

35/309

TINA Handbook

(.2. Custoers6 subodule

The Agencs :ustomers7:lients can be either from a :orporation or 5eseller or can be

individuals. 6oth :orporations and 5esellers are :ompanies. The :ustomers7:lients who are


:orporate :ustomers) 5eseller :ustomers and individual :ustomers are listed together in

the :ustomers administration page

(.2.1. 5ain page description

This sub+module has a main page named P:ustomers administration.

It shows the list of the Travel Agenc :lient :ustomers. *ach :ustomer that the Agenc

serves must be recorded into the database along with its details. All records are saved for

travel operations) future reports and travel agenc log.

The list can be searched and filtered for showing onl those :ustomers that correspond to

desired criteria

-ig. The :ustomers administration page

The :ustomers can be sorted according to different criteria 3name) adding date4

Above the list there is a tab that opens the filter menu named C:ustomers filtersD and in the

right side there is a button named FAdd :ustomerG used to add new elements.

The column heads colored with blue can be clicked to sort the list by that column. The sort can

be ascending on descending with every click on the column head.

The C:ompanD column includes an informational smbol for each record. 0hen accessed)the smbol opens a window with compan data.

(.2.2. 4ptions $or Custoers

-ig.

8/21/2019 TINA_manual_EN_24.01.2011

36/309

TINA Handbook

+ opens a new window allowing the User to administrate the :ustomers freuent

buer cards. -or details about freuent fler cards administration see chapter, '.".

+ opens a window with :ustomer profile details) a set of preferences that the

(assenger reuested for his travel services. -or details about (assenger profile see

chapter,'.".E

+ copies some :ustomerSs details such as, last name) telephone) address) deliver

address or zip code for a new famil member of the e/istent :ustomer

+ blocks the corresponding :ustomer making it unable for future usage in travel

operations. 0hen the :ustomer is blocked the smbol turns into meaning that it can

now be used to unblock him.

+ opens the edit menu for the corresponding :ustomer. It opens a window which

allows :ustomer data change. -or details about how to edit a :ustomer see chapter,

'."."

+ deletes the corresponding :ustomer

A :ustomer can be deleted onl if he7she has not been present into a travel action.

(.2.3. -iltering and searching in the Custoers list

In order to show onl the desired :ustomers from the whole list) the User will adust the

filters according to different criteria.




-ig. :ustomers filters menu

-iltering can be made based upon " criteria categories,

:lient tpe, select between all customers) direct customers or customers associated to a

compan. In case of corporation and reseller customers the :ompan name must be

entered. This :ompan field is an autosearch field. -or details about autosearch fields

see chapter,".'.$

:lient name, the User inserts the first name or the last name or a part of the name he

wants to find. In case he knows the e/act name of the :ustomer he can insert both

names

Te/t filter, the User inserts the first word or a part of the first word from, comments) the(N: or the beginning of the (N:) the e+mail or the customer internal id

(assport number, search the :ustomer b his passport number

!ersion ".#$.#.#%&' (age $E of $&%

8/21/2019 TINA_manual_EN_24.01.2011

37/309

TINA Handbook

(.2.(. Adding a Custoer


operation.

8/21/2019 TINA_manual_EN_24.01.2011

38/309

TINA Handbook

1egment, places the :ustomer in one of the defined segments. If not) the segment can

be left in default position.

"f the &ustomer belongs to a &orporation or a >eseller, the &ompany name must be entered in

the corresponding field.

"f the &orporation+>eseller does not eBist in the database, the *ser can use the shortcut button

CD7&orporationE or D7>esellerEF to add it right away. $or details about &orporation+>eseller addition see

chapter3 .!.2

The adding form contains $ more optional areas, personal information) contact data) special

information which can be opened b clicking on their name. These areas look like in the

picture below,

!ersion ".#$.#.#%&' (age $J of $&%

8/21/2019 TINA_manual_EN_24.01.2011

39/309

TINA Handbook

-ig. New :ustomer adding form secondar areas


(ersonal information, birthda) I> data) residence countr) comments) etc)

:ontact data, e+mail) telephone) mobile) fa/) address) deliver address

1pecial information, financial data



8/21/2019 TINA_manual_EN_24.01.2011

40/309

TINA Handbook


be detected by the Application. The adding process will only be possible after necessary corrections.

A :ustomer can be introduced more than once in the database because there can be more than

one person with the same name. However) to avoid the situation when the User adds the same persontwice b accident) it is recommended to insert other distinctive data like (N: 3personal numerical code4

or address when adding :ustomers to the database.

(.2.+. "diting a Custoer

To edit a :ustomer data the User will access the smbol from :ustomers options area

3-or smbol description see chapter, '."."4. A window will open containing a form with

several fields about the :ustomer. The User can edit the inputted data or he7she can insert

new information.

After data modification) the User should press the F*ditG button to finish the process.(ressing F*scapeG from the keboard or the F:ancelG button from the window cancels the

process and closes the edit window

Any error in field input will be detected by the Application. The edit process will only be possible

after necessary corrections.

(.2.,. 7assenger pro$ile

As part of the integrated :59 3:ustomer 5elationship 9anagement4) this option allows the

User to build the (assenger profile) based on different criteria. Accessing the smbolfrom :ustomers options area will open a window with $ sections. 3-or smbol description

see chapter,'."."4

.2.?.!. %ervice fee and discount administration

This section allows the administration of the (assenger 1ervice fee and >iscount profile.

The C1ervice fee K discountD section allows the User to predefine a pricing polic that the

Travel Agenc has settled with the corresponding (assenger) for each 1ervice) for each

calculation mode.

-or each e/istent criterion) the fields below are completed with the proper values 3positive ornegative4. 0hen adding an offer for a service with a defined service fee7discount scheme)

the grid is browsed and the algebraic sum of each criterion is calculated. >epending on each

service fee calculation method) is the sum of the gross valued or limited to a ma/imum value

3if the amount e/ceeds the ma/imum value defined4 and appl this result as service fee for

the new offer.

This option is available onl in TINA

!ersion ".#$.#.#%&' (age '& of $&%

8/21/2019 TINA_manual_EN_24.01.2011

41/309

TINA Handbook

-ig. 1ervice fee profile

-ig. >iscount profile

The service fee profile for the ticketing service is treated in a special wa) meaning that the

service has more criteria than other service as it can be seen in the image below,

!ersion ".#$.#.#%&' (age '# of $&%

8/21/2019 TINA_manual_EN_24.01.2011

42/309

TINA Handbook

This information input can optimi4e the overall process because the *ser does no longer have

to insert it each time in the offering stage. All data entered here can be modified in the offering

process.

In the above picture there are $ geographical areas, >omestic) *urope and Intercontinental

corresponding to different financial policies. These areas are worldwide available.

1ervice fee and >iscount profiles can be set for :orporations) :orporations segments)

(assengers and (assengers segments. In all cases the :orporation profile overrides the (assenger

profile. If all are set) the segment profile is overridden b :orporation7(assenger profile. If none is set)

the default profiles appl. The default :orporation7(assenger profile is overrides b the default

passenger profile

These policies are applied into the 1ervice

8/21/2019 TINA_manual_EN_24.01.2011

43/309

TINA Handbook

.2.?.2. General preferences

-ig. (assenger profile administration

>ifferent options can be selected for the currentl selected (assenger) regarding flightpreferences) food) hotel rental) car rental preferences.

8/21/2019 TINA_manual_EN_24.01.2011

44/309

TINA Handbook

-ig. 1ervice preferences

(.2.. -re;uent buyer cards adinistration 1

The Application can store several freuent buer cards for each (assenger. The recordsremain in the database for the User to appl different discount policies) according to card

settlements.

:ards can be from various suppliers. The 1ervice tpe) card number and 1upplier are

needed for new card addition.

-ig. -reuent buer cards administration

(.3. *uplicate corporate6 subodule

The duplicate corporate section allows the User to match entities that have been introduced

several times in the database and in different was) because) used properl) eliminates all

the records for the same entit.

(.3.1. -iltering and searching in the *uplicate corporate list

In order to show onl the desired :orporations75esellers from the whole list) the User will

adust the filters according to different criteria.




#This option is available onl in TINA

!ersion ".#$.#.#%&' (age '' of $&%

8/21/2019 TINA_manual_EN_24.01.2011

45/309

TINA Handbook

-ig. >uplicate corporations filters menu

-iltering can be made based upon ' criteria,

:ompan tpe, shows onl the :orporations or 5esellers) depending on the selector

:ompanies, shows onl the :ompanies that are set as main) onl the :ompanies that

have associations or onl the :ompanies without associations

The compan alias, the User selects the wa to search in the field and after that enters

the name to filter b

The compan name, the User selects the wa to search in the field and after that enters


(.3.2. 5atching the Copanies

The User selects first the main record on which all the operational activit will be reportedfrom the time ou match the selected information) and after that associate the records thatwill be related to the main one as it can be seen in the picture below,

(.(. *uplicate custoers6 subodule

The duplicate customers section allows the User to match entities that have been introduced

several times in the database and in different was) because) used properl) eliminates all


(.(.1. -iltering and searching in the *uplicate custoers list

In order to show onl the desired :ustomers from the whole list) the User will adust the

filters according to different criteria.




!ersion ".#$.#.#%&' (age 'B of $&%

8/21/2019 TINA_manual_EN_24.01.2011

46/309

TINA Handbook

-ig. >uplicate customers filters menu

-iltering can be made based upon $ criteria,

The customer last name, the User selects the wa to search in the field and after that

enters the name to filter b

The customer first name, the User selects the wa to search in the field and after that

enters the name to filter b

(assengers, shows onl the (assengers that are set as main) onl the (assengers that

have associations or onl the (assengers without associations

(.(.2. 5atching the Custoers


!ersion ".#$.#.#%&' (age 'E of $&%

8/21/2019 TINA_manual_EN_24.01.2011

47/309

TINA Handbook

+. The 'uppliers6 odule

+.1. 5ain page descriptionThis module includes two main sections,

1uppliers section

1ervices section

-ig. 9ain menu

In the left side there is the 1uppliers list sorted according to different criteria 3adding date)

trust) or :ompan name4 and in the left side are listed the offered 1ervices b all 1uppliers.

Above each of the two sections 31uppliers and 1ervices4 is a tab that opens the filter menu

for each section and a button used to add new elements. The buttons are named Fadd1upplierG and Fadd 1erviceG respectivel.

6oth lists can be searched) sorted and filtered for showing onl those 1uppliers or 1ervices

that correspond to desired criteria.

+.2. 'uppliers6 section

It shows the list of the travel agenc 1uppliers. *ach 1upplier that the agenc collaborates

with must be recorded into the database along with its details. All records are saved for

travel operations) future reports and travel agenc log.

+.2.1. 4ptions $or 'uppliers

-ig.

8/21/2019 TINA_manual_EN_24.01.2011

48/309

TINA Handbook

+ opens the 1ervice add menu for the corresponding 1upplier. It allows uick access

to 1ervice adding. The adding process can also be made b selecting the 1upplier from

the left side and then pressing the Fadd 1erviceG button from above the 1ervices

section. -or details about 1ervice adding see chapter, B.".$.$

+ opens a window with 1upplier codes administration. It allows the User to insert the

alphanumerical and the numerical IATA code.

+ opens a window with 1upplier profile details) including due date) commission polic)

invoice restrictions. -or details about 1upplier profile see chapter, B.".".$

+ blocks the corresponding 1upplier making it unable for future usage in travel

operations. 0hen the 1upplier is blocked the smbol turns into meaning that it can

now be used to unblock the 1upplier

+ opens the :ontact (ersons administration menu for the corresponding 1upplier. -or

:ontact persons administration see chapter, B.".".'

+ opens the edit menu for the corresponding 1upplier. It opens a window which allows

1upplier data change. -or details about how to edit a 1upplier see chapter, B."."."

+ deletes the corresponding 1upplier

A 1upplier can be deleted onl if it has not been present into a travel action.

+.2.2. -iltering! sorting and searching in the 'upplier list

In order to show onl the desired 1uppliers from the whole list) the User will adust the filters

according to different criteria.




-ig. 1uppliers filters menu

-iltering can be made based upon $ criteria categories,

Te/t filter, the User inserts the first word or a part of the first word from, the 1upplier

alias) the trust it belongs to and comments or a number or beginning of a number from

financial data and id in order to filter those elements that compl with these inputs

Trust, shows onl the 1uppliers that are associated with a certain trust

!ersion ".#$.#.#%&' (age 'J of $&%

8/21/2019 TINA_manual_EN_24.01.2011

49/309

TINA Handbook

1upplier, directl select the 1upplier name in order to show it in the list. This is an

autosearch field. -or details about autosearch fields see chapter, ".'.$

:ontract, the filtering process will return onl those 1uppliers that have a contract 3or

not) depending on the filter selection4 with the travel agenc

The results can be sorted in ascending or descending order regarding the add date oralphabeticall b name or trust.

.2.2.!. Adding a %upplier


operation.

8/21/2019 TINA_manual_EN_24.01.2011

50/309

TINA Handbook

-ig. New 1upplier adding form


:ompan, the complete official name of the 1uppliers :ompan. In front and after this

name the User can choose the tpe of :ompan and fiscal terminolog. In case of not

knowing these e/tra details) the User will select the blanks for prefi/ and suffi/ of the

name

*/ample, 1: AT8A1T

8/21/2019 TINA_manual_EN_24.01.2011

51/309

TINA Handbook

:hoosing the right alias for the name is an important matter. It should be an intuitive name) eas

to memorize and use) recognized and associated with the respective name b ever User in the travel

agenc. -uture searches and operations with the corresponding :ompan will be made based on this

alias.

Trust, if the :ompan belongs to a bigger trust) it can be written here

1upplier name in 2>1, the e/act name that can be found in the 2lobal >istribution

1stem

-inancial data, information about financial registration

:it7:ountr) address) zip code) phone) fa/) e+mail) website, :ompan contact data

:ontract, in case the 1upplier has a contract with the travel agenc the User can select

CesD

:omments and remarks, other data concerning the 1upplier

6anking data, bank) bank accounts) etc



8/21/2019 TINA_manual_EN_24.01.2011

52/309

TINA Handbook

-ig. 1upplier profile administration

Tree sections are available in the 1upplier profile menu) selectable b the upper tabs,

Invoice due date for that 1upplier

:ommission for that 1upplier

Invoice restrictions for that :ompan

.2.2..!. 0ue date

The C>ue dateD section allows the User to predefine a rule for calculating the due date on

invoices added for the corresponding 1upplier.

-ig 1upplier profile due date

There are " was of defining the due date,

calculating it b adding a defined number of das from the invoice date

depending on a certain period of the month. The time period can be entered in order to

cover the hole month and then depending on the invoice date it will be selected the time

period and it will be applied the entered due date. The due date is determined b adding

the number of das to the end date of the period. In case the end date of the period does

not e/ist in a certain month 3e.g. the end date of the period is $# and the current monthhas $&das4 the due date will be calculated depending on the da $&.

!ersion ".#$.#.#%&' (age B" of $&%

8/21/2019 TINA_manual_EN_24.01.2011

53/309

TINA Handbook

The Application will automaticall input the calculated due date when adding a supplier

invoice.

This information input can optimi4e the overall process because the *ser does not longer have

to insert it each time in the invoice form. All data entered here can be modified in the invoice

generation process.

.2.2..2. &ommission

The P:ommissionD section allows the User to predefine the default commission polic that

the Travel Agenc has settled together with the corresponding 1upplier) according to a

contract.

-ig. 1upplier profile commission

The commission represents one of the two components of the Agenc income. It can be

managed in two was,

As included in the 1upplier price 3select CesD in commissionable selector4 the amount

mentioned in the commission field is alread included in the 1upplier price. Therefore the

value helps when forecasting the amounts that are e/pected in return from the

respective 1upplier

As additional sum over the 1upplier price 3select CnoD in commissionable selector4 the

amount mentioned in the commission field is added over the 1upplier price.

-or both was The User can set a default amount in percentage in the above field

named :ommission amount

There are again two possible was to process the net commission) when selecting CnoD in

the commissionable selector,

>irect calculation 3 from the supplier price4 + the amount represents the percentage

directl from the 1upplier price

The percent applies from the service price + the commission represents the percentage

of the basic 1ervice price) as interpreting it after commission addition

.2.2... "nvoice restrictions

The PInvoice restrictionsD section allows the User to administrate the restrictions regarding

the currencies and the currencies e/change tpes on the invoice and offer for the

corresponding 1upplier.

!ersion ".#$.#.#%&' (age B$ of $&%

8/21/2019 TINA_manual_EN_24.01.2011

54/309

TINA Handbook

8/21/2019 TINA_manual_EN_24.01.2011

55/309

TINA Handbook

Accessing the smbol from 1uppliers options area will open a window like the one below

containing a list with all :ontact (ersons introduced for that 1upplier. 3-or smbol

description see chapter,B.".".'4

-ig. :ontact (ersons administration window

6 pressing the FAdd :ontact (ersonG button) a form window opens with several fields

about the new :ontact (erson.


can be left blank.




After successful adding) the new :ontact (erson shall appear in the :ontact (ersons list.


be detected by the Application. The adding process will only be possible after necessary corrections

8ike in 1uppliers subsection) a few options are available for :ontact (ersons 3 ) ) 4 with

same meanings, show details) edit person data) delete :ontact (erson respectivel.

+.2.3. 'ervices6 section

It shows the list of the predefined 1ervices offered b the travel agencs 1uppliers. *ach

1ervice can be recorded into the database along with its details) depending on its tpe. All

records are saved for travel operations) future reports and travel agenc log.

"ntroducing predefined %ervices for %uppliers is an optional operation.

8/21/2019 TINA_manual_EN_24.01.2011

56/309

TINA Handbook

+ opens a window with 1upplier service profile details) including commission polic

+ opens the edit menu for the corresponding 1ervice. It opens a window which allows

1ervice data change. -or details about how to edit a 1ervice see chapter, B.".$

+ deletes the corresponding 1ervice

A 1ervice can be deleted onl if it has not been present into a travel action

.2..2. $iltering and searching in the %ervice list

In order to show onl the desired filters from the whole list) the User will adust the filters

according to different criteria.



elements listed, he+she must reopen the filter menu

-ig. 1ervice filtering menu


Te/t filter, the User inserts the first word or a part of the first word from, the 1upplier

alias) product name) description and comments in order to filter those elements that

compl with these inputs

1upplier, directl select the 1upplier name in order to show in the list onl the 1ervices

belonging to it. This is an autosearch field. -or details about autosearch fields see

chapter,".'.$

8ocation, the list will contain onl the 1ervices available in the selected location. This is

an autosearch field. -or details about autosearch fields see chapter, ".'.$

Iy selecting a %upplier from %uppliers list the %ervices list from the right side gets automatically

filtered by the selected %upplier.

.2... Adding a %ervice

In order to add a new 1ervice for a 1upplier the User can press the FAdd 1erviceG button

from upper left right side of the main page) in the 1ervices section. A new window openscontaining a form where the User can input relevant data about the new 1ervice.

!ersion ".#$.#.#%&' (age BE of $&%

8/21/2019 TINA_manual_EN_24.01.2011

57/309

TINA Handbook

The %ervice adding form varies according to %ervice type Caccommodation, transportation,

etc.F. The /%ervice1 field is common in all %ervice forms and lets the *ser select which type of %ervice

wants to add.

The necessar details for a 1ervice depend on its tpe and definition mode. The ApplicationAdministrator shall define all aspects of 1ervices 3fields) calculation modes) etc.4 according to Agenc

polic. -or further details about 1ervices definition please contact the Application Administrator.

The fields from the adding form can be different from the ones described here. However an

e/ample of accommodation 1ervice adding shall be given in order to describe the overall

concept.

8/21/2019 TINA_manual_EN_24.01.2011

58/309

TINA Handbook

-ig. Accommodation 1ervice add form


-or accommodation 1ervice) in this case) the following fields are mandator,

1ervice, the selector for 1ervice tpe. CHotelD is now selected

:ategor, the hotel categor

The other fields are optional but can be useful for detailed 1ervice description

!ersion ".#$.#.#%&' (age BJ of $&%

8/21/2019 TINA_manual_EN_24.01.2011

59/309

TINA Handbook

Hotel name, the name of the hotel defined in this 1ervice. Although it is not a mandator

field) it is important because this description can be browsed for offering. 3*/ample,

name of the hotel CTheatre destination, the location where the 1ervice is available. This is an autosearch field. -or

details about autosearch fields see chapter, ".'.$

>escription, a description about the 1ervice. Although it is not a mandator field) it is

important because this description can be browsed for offering.

8ocalization, details about hotel location

Address) telephone) fa/) e+mail, hotel contact data

:omments, e/tra details about the hotel

1uppliers, the alias of the 1ervices 1upplier or 1uppliers. This is an autosearch field.

-or further details about autosearch fields see chapter, ".'.$

1ervice facilities, clicking the mouse over the title) an e/tra form section opens) allowingselecting special features available for that hotel. This list is configurable from CAdminD

module.

-ig. 1ervice facilities form


can be left blank.




After successful adding) the new 1ervice shall appear in the 1ervices list.


be detected by the Application. The adding process will only be possible after necessary corrections.

*/ample,

Adding a trip 1ervice

!ersion ".#$.#.#%&' (age B% of $&%

8/21/2019 TINA_manual_EN_24.01.2011

60/309

TINA Handbook

-ig. (articularities for trip 1ervice adding form


*/ample,

Adding a health insurance 1ervice

-ig. (articularities for health insurance 1ervice adding form


*/ample,

Adding a rent a car 1ervice

!ersion ".#$.#.#%&' (age E& of $&%

8/21/2019 TINA_manual_EN_24.01.2011

61/309

TINA Handbook

-ig. (articularities for rent a car 1ervice adding formD


.2... 9diting a %erviceTo edit a 1ervice data the User will access the smbol from 1ervices options area 3-or

smbol description see chapter, B.".#4. A window will open containing a form with several

fields about the 1ervice. The User can edit the inputted data or he7she can insert new

information.

After data modification) the User should press the F*ditG button to finish the process.

(ressing F*scapeG from the keboard or the F:ancelG button from the window cancels the

process and closes the edit window.

Any error in field input will be detected by the Application. The edit process will only be possibleafter necessary corrections.

+.3. *uplicate suppliers subodule

The duplicate suppliers section allows the User to match entities that have been introduced

several times in the database) and in different was) because) used properl) eliminates all


+.3.1. -iltering and searching in the *uplicate suppliers list

In order to show onl the desired 1upplier from the whole list) the User will adust the filtersaccording to different criteria.




-ig. >uplicate suppliers filters menu


The supplier alias, the User selects the wa to search in the field and after that enters


The supplier name, the User selects the wa to search in the field and after that enters


1uppliers, shows onl the 1uppliers that are set as main) onl the 1uppliers that have

associations or onl the 1uppliers without associations

!ersion ".#$.#.#%&' (age E# of $&%

8/21/2019 TINA_manual_EN_24.01.2011

62/309

TINA Handbook

+.3.2. 5atching the 'uppliers


!ersion ".#$.#.#%&' (age E" of $&%

8/21/2019 TINA_manual_EN_24.01.2011

63/309

TINA Handbook

,. The :eservations6 odule

This module is the first operational module and it represents the workspace of the Agent. All

operations regarding travel 1ervices are operated within this module. The last phase) the

invoice document) will be started here and continued in the second operational module)

CInvoicesD.

C5eservationsD includes " sub+modules,

8/21/2019 TINA_manual_EN_24.01.2011

64/309

TINA Handbook

$or imported ticketing %ervices the *ser can access the (rocess from A">) button from the

#rder $orm and assengers and ticketing %ervices details will be imported automatically from A"> file.

$or details about A"> files see chapter3J.!.!.!

?.!.!.!. %tage 23 %ervice offering

files see chapter3J.!.!.!

?.!.!.2. %tage 3 #ffers selection and confirmation

8/21/2019 TINA_manual_EN_24.01.2011

65/309

TINA Handbook

Invoice generation and invoice issuance are two different phases. -irst one restricts onl

5eservation changes and last one restricts all changes. To make changes beond these phases) take

the steps backwards and void the invoices

This stage allows the User to generate invoices for the respective 5eservation for the

:ustomer and finall close the operational ccle. -or details about invoicing process see

chapter,E.$.#&.'

All invoices to :lients are generated from the P5eservations listD sub+module and never from

P:lients invoicesD sub+module because an invoice is alwas linked to a 5eservation. However)

shortcuts in the :lients invoicesD sub+module can redirect the invoice addition from that section

An invoice can contain one or more totall or partiall invoiced 1ervices

8/21/2019 TINA_manual_EN_24.01.2011

66/309

TINA Handbook

-ig. 6lank

8/21/2019 TINA_manual_EN_24.01.2011

67/309

TINA Handbook

The Application will search for the :ustomer in its database and will list all results that are

compatible with the entered group of characters; the User must select from the list the name

of the :ustomer he wants to add on the form.

-or :ustomers linked to a :orporation or a 5eseller) the name of that legal entit will be

shown beside their names. 0hen the mouse cursor is located over the name of one

(assenger7:orporation) a tooltip with additional information about that

(assenger7:orporation will be automaticall shown) as well.

If the :ustomer is not found in the list) the message Cno resultsD will inform the User that the

:lient he searched for does not e/ist in the database.

-ig. Adding an e/isting (assenger on the

8/21/2019 TINA_manual_EN_24.01.2011

68/309

TINA Handbook

-ig. New :ustomer adding form

6efore adding a new :lient on the eservation can be edited later, in the />eservations list1 sub-

module. $or details about >eservation edit see chapter3?..?

?.2.2.. Add undefined assengers

This option is ver useful when the tourism 1ervices are reuested for a large group of

(assengers) in which situation) adding ever (assenger b his first and last name would

reuire a large amount of operating time.

In the left side of the C:lient administrationD section there is an area where the User can

specif the number of (assengers) classified b three criteria 3Adults) :hildren) and Infants4.After inputting proper number values) the User will push the F1aveG button to validate the

new total number of (assengers for this 5eservation.

!ersion ".#$.#.#%&' (age EJ of $&%

8/21/2019 TINA_manual_EN_24.01.2011

69/309

TINA Handbook

-ig. Total (assengers no. panel

Total number of assengers can be changed later from the >eservations list sub-module. %ee

chapter3?..?.

?.2.2..!. #ptions

-or each :lient added on the

8/21/2019 TINA_manual_EN_24.01.2011

70/309

TINA Handbook

#nly the contact persons which are associated with the selected office will be displayed and

seen in #ther details and services section.

*/ample,

As it can be seen in the figure below) b pressing the smbol the :orporation C

8/21/2019 TINA_manual_EN_24.01.2011

71/309

TINA Handbook

?.2.2..2. #ther elements

In the left side of the C:lient administrationD section) there is a panel with " areas,

Total number of (assengers form which allows the User to adust the (A@ b adding

undefined (assengers to the 5eservation. The form automaticall calculates the total

number of (assengers and keeps track of an changes of (assengers change on the

8/21/2019 TINA_manual_EN_24.01.2011

72/309

TINA Handbook

Application to associate the information received from Amadeus 3through AI5 file4 in the

database) the User should operate in each of these three areas) if necessar.

-ig. (assengers and segments recognition

In primar phase) the Application will search all these data received from Amadeus in its

database, the (assengers name) the Airline and the locations composing the itinerar.

1hould an of these be new for the Application) the will be emphasized with red color and

the User must add this data to the database. After proper inputs into the database)

Application will associate the AI5 readings with the database entries.

2reen color marked data has been recognized and the Application makes a suggestion

about how to handle it.

The *ser is free to ignore the suggestion and treat the data as new to the database.

The handling of all data from AI5 file 3(assengers names) Airline) itinerar4 on this form can

be managed from the Cdouble down arrowD smbol in the right side of each one.

After pressing the smbol) a new small window will open for each of these data containing

the (assenger name) Airline) and location respectivel. All these are entered in autosearch

fields allowing the User to select from the database other (assenger name) Airline or

location for the corresponding ticket. -or details about autosearch fields see chapter, ".'.$

Also in these small windows) the Application can make suggestions if it can find matching

data into the database and) most important) the small windows contain adding buttons, FAdd

(assengerG or FAdd 1upplierG for new elements.

The /add1 buttons presented above are shortcuts to /Adding a assenger1 and /Adding a

%upplier1 operations. $or details about how to add a assenger see chapter.2. .$or details about

how to add a %upplier see chapter3.2.2.!

-ig. Add the (assenger to the database

!ersion ".#$.#.#%&' (age " of $&%

8/21/2019 TINA_manual_EN_24.01.2011

73/309

TINA Handbook

Note that the User can insert the 1ervice -ee and discount for that ticket. 0hen multiple tickets

are selected for import) a general value can be copied for all using the C:op same 1ervice fee to all

ticketsD feature. The 1ervice -ee and discount insertion are part of the estination setting this filter the User selects onl those tickets with the entered

destination

-orm of pament, + setting this filter the User selects onl those tickets paid b CcashD)

Ccredit cardD or combination of those two

Agent7

8/21/2019 TINA_manual_EN_24.01.2011

74/309

TINA Handbook

Te/t filter the User inserts the first word or a part of the first word from the (assenger

name) or a ticket number or (N5




The search result will depend simultaneousl upon all the selected criteria. All shown results

compl with the selected criteria in the sorting area.

After proper filters setup) the resulted list will be shown below the filtering button.

-ig. Not processed tickets list

*ver element in this list represents a ticket with all its details, (assenger name) dest

tina_manual_en_24.01.2011

Documents