Cost Model Properties

Apply the following properties when adding or modifying a cost model:

Property	Type	Description
Name	Text field	A short name for the cost model. This name will be used in the list of cost models on the Management > Linguistic Tool Setup > Cost Model Setup > Cost Models page and must be unique.
Description	Text box	A more complete description of the cost model. This description could include, for example, information on when to use this particular cost model.
Source Locale	Drop-down list	The source locale for the cost model.
Vendor	Drop-down list	The vendor to which the cost model applies.
Currency	Drop-down list	The currency in which to compute costs.
Scoping Configuration	Drop-down list	The scoping configuration, and therefore scoping ranges, to apply to this cost model.
Cost per Word for Segment Match Range for each Target Locale	Table of text fields	A table in which to enter costs for levels of translation based on scoping ranges defined in the scoping configuration. For each target locale, fill in the cost per word for each translation memory matched segment category. That is, fill in a cost (if any) for words with ICE (in-context exact), 100% match, a cost for words with lower percentage matches, and so on. The cost assigned to “Repetition” is the cost, if any, for repeated segments (100% match) that were not in the translation memory at the time of project creation. Use Copy and Paste buttons to copy and paste rows of values among locales. The symbol WorldServer accepts for the grouping and decimal symbols depends on the locale specified for the WorldServer interface. For example, when the interface is localized for Germany or other European country, WorldServer expects the grouping symbol to be a period (.) and the decimal symbol to be a comma (,); when the interface is localized for the United States, WorldServer expects the grouping symbol to be a comma (,) and the decimal symbol to be a period (.). WorldServer processes a numeric string to allow a grouping symbol and a decimal symbol for each value, and ignoring and processing out extraneous symbols, depending on the localization of the user interface. For example, 1,0.1.0 would be interpreted as 10.1 in the United States and 1,0 in a European country.