> For the complete documentation index, see [llms.txt](https://help.sequorplatform.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sequorplatform.io/documentacao/documentation-en/registrations/registrations-backoffice/team-registration.md).

# Team Registration

#### Team Management in Sequor MES

The **Team Registration** allows employees from the same area, line, or production process to be grouped, organizing work in a structured and traceable way.

Teams are used by Sequor MES to **control production entries, calculate indicators (OEE, efficiency, availability)** and facilitate people management and operating costs.

#### Purpose of the registration

The purpose of team registration is **to link people, skills, and locations** within a production structure, ensuring that all operations carried out on the shop floor are associated with the correct team.

With this, the system can:

* Consolidate productivity information by team;
* Monitor performance indicators in a segmented way;
* Assign responsibilities and track activities by group;
* Calculate operating costs based on the configured hourly rate.

> 💡 **Tip:** each employee can be linked to one or more teams, depending on the type of process and work shift.

## 1. Access to the module

In the Sequor MES main menu, go to:\
**Registrations → Teams**

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FQEJHzSK9nfcGO0AngYVE%2F1%20-%20Icone%20cadastro%20equipe.png?alt=media&amp;token=7b4c51ab-09ba-4ddb-ba33-e0ca93356b04" alt=""><figcaption><p>Icon - Team Registration</p></figcaption></figure>

### 1.1. Initial listing screen

When you click the icon, the home screen displays all registered teams, showing the following columns:

| Field             | Description                                                 |
| ----------------- | ----------------------------------------------------------- |
| **Team Number**   | Unique team identifier (defined by the user).               |
| **Team Location** | Plant or unit where the team works.                         |
| **Description**   | Group name or function (e.g.: Maintenance, DLI Production). |

At the bottom of the screen, the system displays the **total number of records** and the **response time** of the query are displayed.

> 💡 **Tip:** use the filter field at the top to quickly locate teams by name, plant, or description.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2F7MiAFJOtQAuVob53E3s6%2F2%20-%20tela%20criteria.png?alt=media&amp;token=9992eab5-8411-4a5c-868f-1b9bef85b853" alt=""><figcaption><p>Criteria Screen - Team Registration</p></figcaption></figure>

#### Action buttons

In the upper right corner of the screen, the main actions are available:

| Icon | Function               |
| ---- | ---------------------- |
| ➕    | **Add new team**       |
| ✏️   | **Edit selected team** |
| 🗑️  | **Delete team**        |

> ⚠️ **Attention:** before deleting a team, check whether it has links to entries, people, or active production orders.

## 2. Team Registration Tabs

When creating or editing a team, the system displays four configuration tabs:

### 2.1. Tab **Team | Header Data**

In this tab, the **basic team identification data**.

| Field                | Description                                                   |
| -------------------- | ------------------------------------------------------------- |
| **Team Number**      | Unique identification code for the team (e.g.: MES-PROD-001). |
| **Team Description** | Team or work group name (e.g.: Production Team 001).          |

> 💡 **Tip:** use a standard format to name teams — for example: *MES-SECTOR-NUMBER* (MES-ASSY-001).

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FYYZqJ2HMRJUCMOZML8pI%2F3%20-%20ABA%20CABE%C3%87ALHO.png?alt=media&amp;token=7f06727e-876d-4abd-8396-0349d4f84067" alt=""><figcaption><p>Header Data Tab - Team Registration</p></figcaption></figure>

### 2.2. Tab **General**

In this tab, the **team location and cost data**.

| Field                        | Description                                             |
| ---------------------------- | ------------------------------------------------------- |
| **Team Location**            | Plant or unit where the team is allocated.              |
| **Status (Active/Inactive)** | Defines whether the team is enabled for use.            |
| **Description**              | Optional field for additional notes.                    |
| **Price/Hour**               | Team hourly cost value, used in operating cost reports. |
| **Currency**                 | Monetary unit (e.g.: BRL/h, USD/h).                     |

> 💡 **Technical tip:** the field *Price/Hour* is used in cost and productivity reports — keep this value updated according to internal adjustments.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FsUL25rnFGH1RmwrM2qCU%2F4%20-%20ABA%20GERAL.png?alt=media&amp;token=b8482543-717d-4570-923d-870bd1f05080" alt=""><figcaption><p>General Tab - Team Registration</p></figcaption></figure>

### 2.3. Tab **Skill**

Allows registering **skills and certifications** that apply to the team as a whole (not just to individuals).

This information helps with traceability of compliance and group training.

| Field                 | Description                                                         |
| --------------------- | ------------------------------------------------------------------- |
| **Skill Name**        | Certification or requirement name (e.g.: NR10, B driver's license). |
| **Skill Description** | Details or purpose of the certification.                            |
| **Valid from date**   | Start date of the certification's validity.                         |
| **Expiration date**   | Final expiration date of the certification.                         |

> **Best practices:**
>
> * Register group certifications required by standard or audit (e.g.: NR10, NR12).
> * Use this registration to centralize team training controls.
> * Update expiration dates periodically.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FICUyoUfU25Me6f6ZifF7%2F5%20-%20ABA%20HABILIDADE.png?alt=media&amp;token=8453754f-96f5-4259-a035-bbe2afc0ae19" alt=""><figcaption><p>Skill Tab - Team Registration</p></figcaption></figure>

### 2.4. Tab **Person**

In this tab, the **team members**, linking the previously created person records.

| Field             | Description                       |
| ----------------- | --------------------------------- |
| **Person Number** | Employee code (e.g.: MES-001).    |
| **Person Name**   | Operator's full name or nickname. |

> 💡 **Tip:** use the ➕ button to add new members to the team.\
> The link between person and team is essential for traceability of records and indicators.

<figure><img src="https://2582153898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwAMVKtJedtiJ4RrzXGfp%2Fuploads%2FmISilDOzDVPB7fhcLDbj%2F6%20-%20ABA%20PESSOA.png?alt=media&amp;token=08224413-4868-437d-8c76-9a6d0baff894" alt=""><figcaption><p>Person Tab - Team Registration</p></figcaption></figure>

> After creation, the team will be available for selection in production entries, reports, and efficiency controls in Sequor MES.

## 3. Best practices

* Keep **standardized team names** to facilitate management and searching.
* Periodically review the **linked members** and the **active skills**.
* Avoid duplicates — the same team should not be registered in more than one plant.
* Update the **hourly cost** whenever there are salary or structural changes.
* Use the status **Inactive** for discontinued teams, avoiding loss of history.
