Introduction
This article provides background information about using various Costs & Metrics reports and analyzing related problems.
To display Cost & Metrics reports, select Projects → Project list → Actions → (choose) → Reports → Costs and metrics. In this section, you can choose more specific forms that contain actual information.
Description of Costs and metrics reports
Assignment and words
| |
|---|
The Assignment and words report lists all specified projects within which jobs are aggregated (grouped) by a specific source and target language combination. For example, if you have a project that contains two target languages, two source files, and two workflow steps to which you have assigned Linguists (you have four XTM Cloud jobs in total), and you include it in the report, the report will only contain two entries, each for a single source and target language combination. The report itself covers active, finished, and archived projects. Its purpose is to show user assignments, total word count and the total manual time spent on a particular source and target language combination, in a particular XTM Cloud project. This report is particularly useful to deep-dive into your vendor productivity metrics, because it enables you to compare the project scope against the expected due date and actual time spent on a task. Since this type of report does not contain any cost-related data, the report itself does not require generating costs, to be generated successfully. | Year quarter → The year-quarter in which the project was created in XTM Cloud. Year-month → The year-month in which the project was created in XTM Cloud. Project name → The project's name in XTM Cloud. Description → Description of the project in XTM Cloud (if that description exists). Creator → The Project manager who created the project in XTM Cloud. Customer → The XTM customer for which the project was created in XTM Cloud. Project ID → The project's ID in XTM Cloud. Creation date → Date that the project was created in XTM Cloud, in DD-MM-YYYY format. Due date → Due date set for the project in XTM Cloud (if specified). Project manager → Project manager assigned to the project in XTM Cloud. [Custom field names] → Custom fields used in the project (if any). Source language → Source language for a particular aggregated job. Target language → Target language for a particular aggregated job. [Workflow Steps Assignees] → Shows the assignees for a particular workflow step. The number of these columns depends on the workflow complexity. [Workflow Steps Time] → Total manual time spent on a particular workflow step. The number of these columns depends on the workflow complexity. Total word count → Total source word count for a particular aggregated job. Hours → Total manual time spent on a particular aggregated job, in HH-MM format.
|
Costs and words per customer or custom field
| |
|---|
The Costs and words per customer or custom field report lists all specified projects and provides the total sum of costs generated, source words, and hours taken, per XTM Cloud project. For example, if you have a project that contains two target languages, two source files, and two workflow steps to which you have assigned Linguists (you have four XTM Cloud jobs in total), and you include it in the report, the report will contain only one entry (since it there is only one project in total). The report itself covers active, finished, and archived projects. Its purpose is to show the sum of costs generated, source words, and hours taken, per XTM Cloud project, as well as the total for the costs, word count, and hours, of all projects in the columns. This report is particularly useful whenever you want to have an overview of the project scope and costs across multiple customers. The real benefit of this report is represented by the grouping options, which enable you to flexibly divide the data in different sections, either based on customer or custom fields. | Information about grouping: Customer → XTM customer for which the project was created in XTM Cloud. [Custom field names] → Custom fields that were used in the project (if any). Sum of costs + currency → Sum of costs generated for the project. Sum of words → Sum of source words for the project. Sum of hours → Sum of hours taken. Project cost warnings → This column is only displayed if you have selected the “Include costs with warnings in Cost and metrics reports” checkbox. It indicates whether costs have been generated correctly or with warnings. The values are: Yes → The cost has been generated with warnings. Costs generated with warnings are marked with the exclamation mark icon in Project Editor → Estimates → Costs. No → The cost has been generated correctly.
There is also the Total row for the selected values for all projects in the columns, which shows the total sum of costs, source words, and hours. |
Costs and metrics per Linguist
| |
|---|
The Costs and metrics per Linguist report lists all specified projects and provides aggregated metrics/statistics/time (depending on the “cost type” selected upon costs generation) and related costs, per Linguist, target language, and type of workflow step. For example, let’s consider a project that contains two target languages, two source files, and two workflow steps (you have four XTM Cloud jobs in total). You have two Linguists and you assign the first one to all the TRANSLATE steps and just one CORRECT step, and the second Linguist only to the remaining CORRECT steps. If you include the project in the report, the report will contain three entries (since the report groups data per Linguist AND workflow step). The report itself covers active, finished, and archived projects. Its purpose is to show aggregated metrics/statistics/time (depending on the “cost type” selected upon costs generation) and related costs per Linguist, target language and type of workflow step. This report is particularly useful whenever you need an overview of your vendor costs and scope covered across multiple projects. | Project ID → The project's ID in XTM Cloud. Project name → The project's name in XTM Cloud. Template → Project template used in the project, in XTM Cloud (if any). [Custom field names] → Custom fields that were used in the project (if any). LSP → Subcontractor assigned to a particular type of workflow step (if any). Linguist → Internal Linguist assigned to a particular type of workflow step, in a particular target language. Source language → Source language for a particular Linguist and type of workflow step. Target language → Target language for a particular Linguist and type of workflow step. Step → Type of workflow step that a particular Linguist is assigned to, in a particular target language. Total word count → Total word count that aggregates source words for a particular Linguist/workflow step/target language combination. ICE match → Total word count that aggregates source words that were ICE-matched for a particular Linguist/workflow step/target language combination. Leveraged match → Total word count that aggregates source words that were Leverage-matched for a particular Linguist/workflow step/target language combination. 95-99% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (95-99%) for a particular Linguist/workflow step/target language combination. 85-94% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (85-94%) for a particular Linguist/workflow step/target language combination. 75-84% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (75-84%) for a particular Linguist/workflow step/target language combination. Repetitions → Total word count that aggregates source words that were matched with Repetitions for a particular Linguist/workflow step/target language combination. 95-99% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (95-99%) for a particular Linguist/workflow step/target language combination. 85-94% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (85-94%) for a particular Linguist/workflow step/target language combination. 75-84% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (75-84%) for a particular Linguist/workflow step/target language combination. Machine translation → Total word count that aggregates source words that were matched with Machine translation for a particular Linguist/workflow step/target language combination. No matching → Total word count that aggregates source words that were not matched with any match type, for a particular Linguist/workflow step/target language combination. Non-translatable → Total word count that aggregates source words that were labeled as non-translatable for a particular Linguist/workflow step/target language combination. Time → Time (manual time tracking) that was taken for a particular workflow step-target language combination, by a particular Linguist, in HH-MM format. Cost → Costs generated for a particular Linguist/workflow step/target language combination. Cur. → Currency used by a particular Linguist. Project cost warnings → This column is only displayed if you have selected the “Include costs with warnings in Cost and metrics reports” checkbox. It indicates whether costs have been generated correctly or with warnings. The values are: Yes → The cost has been generated with warnings. Costs generated with warnings are marked with the exclamation mark icon in Project Editor → Estimates → Costs. No → The cost has been generated correctly.
|
Initial metrics, assignment and costs
| |
|---|
The Initial metrics, assignment and costs report lists all specified projects and provides aggregated initial metrics, user assignment to workflow steps, and related costs, per target language in a particular project in XTM Cloud. For example, let’s consider a project that contains two target languages, two source files, and two workflow steps to which you have assigned Linguists (you have four XTM Cloud jobs in total). If you include the project in the report, the report will contain two entries (since the report groups data per target language). The report itself covers active, finished, and archived projects. Its purpose is to show aggregated initial metrics, user assignment to workflow steps, and related costs, per target language in a particular project in XTM Cloud. This report is particularly useful whenever you need to focus your cost and metrics analysis on the initial project metrics (coming from the first project analysis) instead of the most up to date metrics. You can use this report also to potentially compare the initial scope (initial metrics) with the current scope (current metrics reports). IMPORTANT! The Initial metrics here actually reference the most recent analysis event for the project. For example, imagine that you create a project with no matching segments at all, translate it and then reanalyze it. All segments will be assigned ICE matches and this will be reflected in the Current Metrics and the "Reanalysis" event in the Metrics history. Costs based on Initial metrics will be based on ICE matches. | Year quarter → The year-quarter in created in XTM Cloud. Year-month → The year-month in which the project was created in XTM Cloud. Customer → The XTM customer for which the project was created in XTM Cloud. Project ID → The project's ID in XTM Cloud. Project name → The project's name in XTM Cloud. Creator → The Project manager who created the project in XTM Cloud. Creation date → Date that the project was created in XTM Cloud, in DD-MM-YYYY format. Due date → Due date set for the project in XTM Cloud (if specified). Project manager → Project manager assigned to the project in XTM Cloud. [Custom field names] → Custom fields that were used in the project (if any). Source language → Source language for the project in XTM Cloud. Target language → Target language for the project in XTM Cloud. Total word count → Total word count that aggregates source words for a particular target language in a particular project in XTM Cloud. New words → Number of source words except for the ones that were not ICE-matched or Leverage-matched. 100% matched words → Number of source words that were ICE-matched or Leverage-matched. Non-matched words → Number of source words without any TM match. Non-translatable → Number of source words which are labeled as non-translatable for a particular target language in the project. Alphanumericwords → Number of source non-translatable words that are alphanumeric, for a particular target language in the project. Measurewords → Number of source non-translatable words that denote units of measurement, for a particular target language in the project. Numericwords → Number of source non-translatable words that are numeric, for a particular target language in the project. Punctuationwords → Number of source non-translatable words that are used as punctuation, for a particular target language in the project. To be done → Number of source words that have not been translated yet, in a particular target language of the project. ICE match → Total word count that aggregates source words that were ICE-matched for a particular target language in the project. Leveraged match → Total word count that aggregates source words that were Leverage-matched for a particular target language in the project. 95-99% Fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (95-99%) for a particular target language in the project. 85-94% Fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (85-94%) for a particular target language in the project. 75-84% Fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (75-84%) for a particular target language in the project. Repeat → Total word count that aggregates source words that were matched with Repetitions for a particular target language in the project. 95-99% Fuzzy repeat → Total word count that aggregates source words that were matched with Fuzzy Repetition (95-99%) for a particular target language in the project. 85-94% Fuzzy repeat → Total word count that aggregates source words that were matched with Fuzzy Repetition (85-94%) for a particular target language in the project. 75-84% Fuzzy repeat → Total word count that aggregates source words that were matched with Fuzzy Repetition (75-84%) for a particular target language in the project. Machine translation → Total word count that aggregates source words that were matched with Machine translation for a particular target language in the project. [Workflow Steps Assignees] → Shows all the users assigned to a particular type of workflow step, in a particular target language. The number of “workflow steps assignees” columns depends on workflow complexity. [Workflow Steps Time] → Shows the total time spent by Linguists on a particular workflow step, in a particular target language. The number of “workflow steps time” columns depend on workflow complexity. [Workflow Steps Costs] → Shows the total costs generated for a particular type of workflow step, in a particular target language. The number of “workflow steps costs” columns depends on workflow complexity. Fixed prices / language → Shows the total costs generated for a fixed price, for a single source and target language combination (it is set up in a user rate card, in the “Fixed price per language” field) for a particular target language in the project. Remainder of min. charge / language → Shows the total costs generated for a minimum charge per language, for a single source and target language combination (it is set up in a user rate card, in the “Minimum charge per language” field) for a particular target language in the project. Additional costs / language → Shows the total additional costs generated for a single source and target language combination, for a particular target language in the project. Total language cost → Shows the total costs generated for a particular target language in the project. Total project cost → Shows the total costs generated for the whole project. Cur. → Currency used by a particular Linguist. Project cost warnings → This column is only displayed if you have selected the “Include costs with warnings in Cost and metrics reports” checkbox. It indicates whether costs have been generated correctly or with warnings. The values are: Yes → The cost has been generated with warnings. Costs generated with warnings are marked with the exclamation mark icon in Project Editor → Estimates → Costs. No → The cost has been generated correctly.
|
Metrics, custom fields included
| |
|---|
The Metrics, custom fields included report lists all specified projects and provides aggregated metrics per target language for an XTM Cloud project. For example, if you have a project that contains two target languages, two source files, and two workflow steps to which you have assigned Linguists (you have four XTM Cloud jobs in total), and you include it in the report, the report will contain two entries (since there are two target languages in the project). The report itself covers active, finished, and archived projects. Its purpose is to show aggregated metrics per target language in the XTM Cloud project. This report is particularly useful whenever you want to analyze the current project scope by language. Custom fields can further help you categorize the relevant projects to spot interesting trends. Since this type of report does not contain any cost-related data, the report itself does not require generating costs, to be generated successfully. | Creation date → Date that the project was created in XTM Cloud, in DD-MM-YYYY format. Due date → Due date set for the project in XTM Cloud (if specified). Client name → Company name in XTM Cloud. Customer → The XTM customer for which the project was created in XTM Cloud. Project manager → Project manager assigned to the project in XTM Cloud. Creator → The Project manager who created the project in XTM Cloud. [Custom field names] → Custom fields that were used in the project (if any). Project name → The project's name in XTM Cloud. Project ID → The project's ID in XTM Cloud. Source language → Source language for the project in XTM Cloud. Target language → Target language for the project in XTM Cloud. No matching → Total word count that aggregates source words that remain unmatched for a particular target language in the project. ICE match → Total word count that aggregates source words that were ICE-matched for a particular target language in the project. Leveraged match → Total word count that aggregates source words that were Leverage-matched for a particular target language in the project. 95-99% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (95-99%) for a particular target language in the project. 85-94% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (85-94%) for a particular target language in the project. 75-84% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (75-84%) for a particular target language in the project. Machine translation → Total word count that aggregates source words that were matched with Machine translation for a particular target language in the project. Repeat → Total word count that aggregates source words that were matched with Repetitions for a particular target language in the project. 95-99% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (95-99%) for a particular target language in the project. 85-94% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (85-94%) for a particular target language in the project. 75-84% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (75-84%) for a particular target language in the project. Non-translatable → Number of source words which are labeled as non-translatable for a particular target language in the project.
|
Project cost, metrics per step
| |
|---|
The Project cost, metrics per step report lists all specified projects and provides aggregated costs and metrics/statistics/time (depending on the “cost type” selected upon costs generation) per type of workflow step and target language for an XTM Cloud project. For example, if you have a project that contains two target languages, two source files, and two workflow steps (you have four XTM Cloud jobs in total), and you include it in the report, the report will contain four entries (since there are two target languages in the project, each containing two distinct workflow steps). The report itself covers active, finished, and archived projects. Its purpose is to show aggregated costs and metrics/statistics/time (depending on the “cost type” selected upon costs generation) per type of workflow step and target language of a XTM Cloud project. This report is particularly useful whenever you want to analyze cost and scope trends based on the type of task performed by your vendor (workflow steps). For example, you could analyze DTP costs over time or understand how your post-editing costs have changed across projects. | Project ID → The project's ID in XTM Cloud. Project name → The project's name in XTM Cloud. Customer → The XTM customer for which the project was created in XTM Cloud. [Custom field names] → Custom fields that were used in the project (if any). Subject matter → Subject matter of the project in XTM Cloud (if any). Creation date → Date that the project was created in XTM Cloud, in DD-MM-YYYY format. Due date → Due date set for the project in XTM Cloud (if specified). Workflow Completion Date → Date the workflow was completed, in DD-MM-YYYY format. Step cost → Shows the total costs generated for a particular type of workflow step in a particular target language. Total project cost → Shows the total costs generated for the project in XTM Cloud. Cur. → Currency used by a particular Linguist. Project status → Current status of the project in XTM Cloud. Source language → Source language for the project in XTM Cloud. Target language → Target language for the project in XTM Cloud. Step Name → Name of the workflow step. Chargeable → Determines whether or not that type of workflow step is subject to charge. Total word count → Total word count that aggregates source words for a particular type of workflow step, in a particular target language. ICE match → Total word count that aggregates source words that were ICE-matched for a particular type of workflow step, in a particular target language. Leveraged match → Total word count that aggregates source words that were ICE-matched for a particular type of workflow step, in a particular target language. 95-99% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (95-99%) for a particular type of workflow step, in a particular target language. 85-94% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (85-94%) for a particular type of workflow step, in a particular target language. 75-84% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (75-84%) for a particular type of workflow step, in a particular target language. Repetitions → Total word count that aggregates source words that were matched with Repetitions for a particular type of workflow step, in a particular target language. 95-99% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (95-99%) for a particular type of workflow step, in a particular target language. 85-94% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (85-94%) for a particular type of workflow step, in a particular target language. 75-84% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (75-84%) for a particular type of workflow step, in a particular target language. Machine translation → Total word count that aggregates source words that were matched with Machine translation for a particular type of workflow step, in a particular target language. No matching → Total word count that aggregates source words that remain unmatched for a particular type of workflow step, in a particular target language. Non-translatable → Number of source words which are labeled as non-translatable for a particular type of workflow step, in a particular target language. Time → Time (manual time tracking) that was taken for a particular type of workflow step, by a particular Linguist, in HH-MM format. Finish date → Date of finishing a particular type of workflow step, in a particular target language, in DD-MM-YYYY format. Project cost warnings → This column is only displayed if you have selected the “Include costs with warnings in Cost and metrics reports” checkbox. It indicates whether costs have been generated correctly or with warnings. The values are: Yes → The cost has been generated with warnings. Costs generated with warnings are marked with the exclamation mark icon in Project Editor → Estimates → Costs. No → The cost has been generated correctly.
|
Project cost, metrics, and assignment per step
| |
|---|
The Project cost, metrics per step report lists all specified projects and provides aggregated costs and metrics/statistics/time (depending on the “cost type” selected upon costs generation), and user assignment, per type of workflow step and target language for an XTM Cloud project. For example, if you have a project that contains two target languages, two source files, and two workflow steps to which you have assigned Linguists (you have four XTM Cloud jobs in total), and you include it in the report, the report will contain four entries (since there are two target languages in the project, each containing two distinct workflow steps). The report itself covers active, finished, and archived projects. Its purpose is to show aggregated costs and metrics/statistics/time (depending on the “cost type” selected upon costs generation), and user assignment, per type of workflow step and target language for an XTM Cloud project. This report is particularly recommended if you use machine translation and are measuring edit distance. This report gives you insights into project cost, scope and edit distance calculation, along with the vendor cost discounts based on edit distance. | Project ID → The project's ID in XTM Cloud. Project name → The project's name in XTM Cloud. Customer → The XTM customer for which the project was created in XTM Cloud. Template → Project template used in the project, in XTM Cloud (if any). Subject matter → Subject matter of the project in XTM Cloud (if any). Created by → Project manager who created the project in XTM Cloud. Creation date → Date that the project was created in XTM Cloud, in DD-MM-YYYY format. Due date → Due date set for the project in XTM Cloud (if specified). Workflow Completion Date → Date the workflow was completed, in DD-MM-YYYY format. Step cost → Shows the total costs generated for a particular type of workflow step in a particular target language. Total project cost → Shows the total costs generated for the project in XTM Cloud. Project status → Current status of the project in XTM Cloud. Source language → Source language for the project in XTM Cloud. Target language → Target language for the project in XTM Cloud. Step Name → Name of the workflow step. Assignee → Users assigned to a particular type of workflow step, in a particular target language. Chargeable → Determines whether or not that type of workflow step is subject to charge. Total word count → Total word count that aggregates source words for a particular type of workflow step, in a particular target language. ICE match → Total word count that aggregates source words that were ICE-matched for a particular type of workflow step, in a particular target language. Leveraged match → Total word count that aggregates source words that were ICE-matched for a particular type of workflow step, in a particular target language. 95-99% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (95-99%) for a particular type of workflow step, in a particular target language. 85-94% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (85-94%) for a particular type of workflow step, in a particular target language. 75-84% fuzzy match → Total word count that aggregates source words that were Fuzzy-matched (75-84%) for a particular type of workflow step, in a particular target language. Repetitions → Total word count that aggregates source words that were matched with Repetitions for a particular type of workflow step, in a particular target language. 95-99% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (95-99%) for a particular type of workflow step, in a particular target language. 85-94% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (85-94%) for a particular type of workflow step, in a particular target language. 75-84% fuzzy rep. match → Total word count that aggregates source words that were matched with Fuzzy Repetition (75-84%) for a particular type of workflow step, in a particular target language. Machine translation → Total word count that aggregates source words that were matched with Machine translation for a particular type of workflow step, in a particular target language. No matching → Total word count that aggregates source words that remain unmatched for a particular type of workflow step, in a particular target language. Time → Time (manual time tracking) that was taken for a particular type of workflow step, by a particular Linguist, in HH-MM format. Finish date → Date of finishing a particular type of workflow step, in a particular target language, in DD-MM-YYYY format. Project cost warnings → This column is only displayed if you have selected the “Include costs with warnings in Cost and metrics reports” checkbox. It indicates whether costs have been generated correctly or with warnings. The values are: Yes → The cost has been generated with warnings. Costs generated with warnings are marked with the exclamation mark icon in Project Editor → Estimates → Costs. No → The cost has been generated correctly.
|
Words, time per Linguist, language and task
| |
|---|
The Words, time per Linguist, language and task report lists all specified projects and provides information about the total number of words and words that have already been translated/processed, per Linguist, source file, target language, and type of workflow step. For example, if you have a project that contains two target languages, two source files, and two workflow steps to which you have assigned Linguists (you have four XTM Cloud jobs in total), and you include it in the report, the report will contain eight entries (since there are two target languages in the project, each containing two source files and four distinct tasks). The report itself covers active, finished, and archived projects. Its purpose is to provide information about total words and words that have already been translated/processed, per Linguist, source file, target language, and type of workflow step. This report is particularly useful if you want to analyze the effort actually invested by your internal linguists (excluding subcontractors) on different projects. What also sets this report apart from the rest is that it can only include internal projects, and tasks assigned to internal Linguists. Unless you select any restrictions in the popup, all currently active tasks will be included. If the Include only unfinished tasks option is not selected, finished tasks will be included as well. Unlike the other reports in this Costs and metrics section, this report can also be used to generate a report based on either source statistics or target statistics. | Project name → The project's ID in XTM Cloud. Project ID → The project's ID in XTM Cloud. File name → Name of the source file. Assignee → User assigned to a particular workflow step. Step name → Name of the workflow step. Target language → Target language for the project in XTM Cloud. Task status → Actual status of the task. Segment → Segment range that a particular Linguist is assigned to, in a particular workflow step. Words received → Total project word count. Words translated / processed → Word count that shows either the total amount of source statistics or target statistics. Time spent on the job (automatic time tracking) [hh:mm:ss] → Time spent on a particular task by a Linguist, in HH:MM:SS format. Time spent on the task (from start workflow to finish workflow) [dd:hh] → Time spent on a particular task by a Linguist, in DD:HH format. Start date → Date that the project was started in XTM Cloud, in DD-MM-YYYY format. Finish date → Date that the project was finished in XTM Cloud, in DD-MM-YYYY format.
|
Correct ways to generate Costs & Metrics reports
| |
|---|
Go to Projects → Project list → Actions. Use the checkboxes to select a specific group of projects. Select the Costs and metrics report from the dropdown list and then the required report type.
| Go to Projects → Project list → Advanced Search. Find a specific group of projects using the selected filters. Go to Projects → Project list → Actions. (After filtering out irrelevant projects, make sure to select the Searched projects only checkbox include the filtered projects in the report, no matter how many there are). Select the Costs and metrics report from the dropdown list and then the required report type.
|
Process of generating the Costs & Metrics reports
XTM Cloud checks if costs have previously been generated in a specific project (you can check this in the Project editor → Estimates → Costs).
1.1. If costs have not been generated before, XTM Cloud forces their generation when it generates the report.
1.2. If costs have been generated before, XTM Cloud checks if they were generated correctly (without warning or error messages).
1.2.1. If the most recent generated costs are correct, XTM Cloud will move them to the Costs & Metrics report.
1.2.2. If the most recent generated costs are incorrect, XTM Cloud will start checking costs that were generated earlier.
1.2.2.1. If any of the previously generated costs are correct, XTM Cloud will move them to the Costs & Metrics report.
1.2.2.2. If none of the previously generated costs are correct, XTM Cloud will force a new costs generating for a specific project.
What are the possible costs generation results when generating a Costs & Metrics report (1.1 and 1.2.2.2)?
If the costs are generated correctly → information about the project will be included in the report.
If the costs are generated incorrectly → the project involved will not be included in the report.
Correctness of costs generation
Correct costs generation is defined as generation without warning or error messages. In Project editor → Estimates → Costs, warning or error messages are represented by a yellow or red icon on the right-hand side of a particular row. When you hover over this tooltip, you will see information about what needs to be reviewed and improved so that the costs can be generated correctly (see Costs generation – most common issues & troubleshooting for more information and troubleshooting guidelines).
Inclusion of costs entries with WARNINGS in Costs & Metrics reports
By default, projects with incorrectly generated costs (yellow or red) are not displayed in Costs & Metrics reports. However, it is possible to include costs entries with WARNINGS (yellow) as well. For this purpose, we can first decide if such a possibility is to be selected by default, in the XTM Cloud UI (Configuration → Data → Estimates → Costs settings → Costs settings → Include costs with warnings in Cost and metrics reports). Administrative privileges are required!
The following reports include an additional option, which you can select if required: Include costs with warnings in Cost and metrics reports.
Costs and words per customer or custom field,
Costs and metrics per Linguist,
Initial metrics, assignment, and costs,
Project costs, metrics per step,
Project costs, metrics and assignment per step.
When you select this option, the following will occur:
Reports will always have a new Project cost warnings column containing YES or NO value.
If costs are correct (blue mark), the column will say NO.
If costs have warnings (yellow mark), the column will say YES, and the report will contain data for the project, including incomplete costs.
For costs with errors (red mark), there will be an attempt to generate costs again. If the generated costs are correct or with warnings, they will be listed in the report. If the costs still have an error, they will be skipped.
How to choose the basis for costs when generating Costs & Metrics reports
Costs can be generated on the basis of metrics (initial/current), statistics (source/target) or manual time tracking. To select the basis for generating costs and Costs & Metrics reports, select Configuration → Data → Estimates → Cost settings → Cost settings → Default cost type.
Good to know!
In the case of any other issues involving generating Costs & Metrics reports, make sure that you have read the article below. It describes and provides troubleshooting tips for the most common causes for incorrect cost generation: Costs & Metrics reports - most common issues & troubleshooting.
