In this article, we will delve into the details of Bureau Works' new Analytics tool, providing a comprehensive guide to its features and functionality.

1. Introduction
2. Quick overview
3. Account_metrics
  3.1 Metric_type
  3.2 Count
4. Account_users
5. Account_users_access
6. Organization_users
7. Org_unit_users
8. Project_costs
9. Project_resources
10. Projects
11. Project_status_changes
12. Project_tags
13. Quality_report
14. Tasks
15. Work_units

1. Introduction

The Analytics is Bureau Works new analytics dashboard, designed to provide users with granular insights into their project data. It can be found in the Tools section.

This tool offers a customizable interface, allowing users to create tailored reports and visualizations based on a variety of metrics and dimensions.

The dashboard and charts leverage a robust underlying data model, providing access to comprehensive datasets that cover various aspects of the Bureau Works platform

2. Quick overview

All datasets and column names try to communicate exactly what they represent. For more complex cases, we will explore these in the specific sections for each dataset. 

In general, timestamps are represented as such or in epoch format, i.e., the number of milliseconds since 1/1/1970. Some datasets will be pre-grouped, and the date reference may be represented as a string, like 2024-08 (YYYY-MM) in the account_metrics dataset.

Some columns will contain JSON data (JSONB in PostgreSQL) and can be queried and used with the appropriate operators.
Ref: https://www.postgresql.org/docs/current/functions-json.html

3. Account_metrics

Provides volume in chars, words, or tokens from Machine Translation engines, AI and pure volume processing. This dataset is organized by YYYY-MM.

3.1 Metric_type

• METRIC_WORK_UNIT - raw volume
• METRIC_MT_TRANSLATION - machine translation volume
• METRIC_MT_GPT_BWX_OPENAI - AI volume

3.2 Count

• When this data is present, its number is inherent to its type. For example, for METRIC_MT_GPT_BWX_OPENAI, the column cnt will represent the number of tokens.

4. Account_users

List all the users in the account, along with their associations with Organization(s) and Organizational Unit(s).

5. Account_users_access

A log with all access by the account users, including IP-based location. Every API hit spaced by at least 15 minutes is logged as a single access. For example, an active user's session during 1 hour may log up to 4 records in the dataset.

6. Organization_users

Same as the account_users, but organized by Organization Name.

7. Org_unit_users

Same as the account_users and organization_users, but listed by Organizational Unit name.

8. Project_costs

A view of the costs, if any, associated with Projects. The description column will have the name of the Price associated with that row. For example:

• description Words Translation 0% - 49%
• match_start 0
• match_end 49
• unit_type WORD
• units 250
• cost_per_unit 0.01
• rate_type NOMINAL
• total 2.50
• cost_type TRANSLATIONS

This data sample shows that for the price in the description, a certain match (net rate) may be calculated based on the pricing configuration in Bureau Works.

9. Project_resources

A list of all resources (files) that have been uploaded to a Project.

10. Projects

A list of all Projects in Bureau Works. All dates are presented in TIMESTAMP format. Some valid notes:

• The creator is the person who created the project, the "requester".
• The assignee is normally the person responsible for the execution of the Project, the Project Manager.
• ci_tag is reserved for Continuous Integration projects and is useful for connectors, such as the GitHub Connector.
• target_languages is a JSON field with all the project languages.

11. Project_status_changes

A log of all the Status transitions recorded in Bureau Works for all Projects. It records the person who created the request for APPROVAL, DELIVERY, etc.

12. Project_tags

A list of all tags that were associated with the project, including the CI tag.

13. Quality_report

Represents the reports of all reviews recorded in Bureau Works. Between workflows, when content is reviewed/modified, these changes and steps are recorded in this dataset, which provides a fine-grained view of the actions performed.

14. Tasks

A list of all Tasks in the system, with detailed information about who created them, to whom they were assigned, project workflow, etc. If costs are calculated and a Payable Amount is present in the Task, it enables profitability/margin calculations.

15. Work_units

Brings a list of all Work Units organized by Project Name, ID, etc. The difference noted between words and net_words, when present, is related to the analysis of the Work Unit based on leverage from the Translation Memories. project_resource_id can be used to match with the project_resources dataset that was previously mentioned.

If any questions were not answered in this article, please don't hesitate to contact our support team at help@bureauworks.com.