# Activities

<figure><img src="https://content.gitbook.com/content/pAbYPeH0IeVsC8b0gI87/blobs/uDTnSK0iZYMvilN83WJk/2025-09-03%2012_05_48-Greenshot.png" alt=""><figcaption><p>Image A</p></figcaption></figure>

The **Activities** section is dedicated to displaying the catalog of activities that can be performed on components during maintenance. Each activity can be linked to certain components and subgroups, in order to specify which objects the activity is carried out on when executed.\
In addition, each activity can be associated with counters that indicate, relative to the last maintenance in which it was performed, when it will need to be repeated.

#### Adding Activities and Counters

<figure><img src="https://content.gitbook.com/content/pAbYPeH0IeVsC8b0gI87/blobs/SkIvYf820Y9EwrvcLoWJ/2025-09-03%2012_06_06-Greenshot.png" alt=""><figcaption><p>Image B</p></figcaption></figure>

The *Add Activity* button allows you to insert a new activity into the database. Image B shows the window where the data can be filled in. The information to be specified is as follows:

* Activity Code: unique code identifying the activity;
* Operators: number of people required to perform the activity;
* Duration: duration of the activity expressed in minutes.
* Translations: the name under which the activity should appear and a short description must be provided in all project languages;
* Counters Aggregation Strategy: this field allows you to select, from a set of predefined functions, which one to use for dynamically choosing the reference counter to determine the component’s useful life;
* Starting Date: this data allows the system to determine the initial moment from which to begin counting in order to propose a date when the activity will need to be performed.

Optionally, one or more counters can be associated with an activity, in order to have an automatic count that indicates when it must be performed.

The button highlighted in Image C allows you to add a counter. For each counter, the following information must be configured:

* Counter Code: unique code identifying the counter;
* Reference KPI: value or formula to be used for counting. Note that usable KPIs depend on the machine’s configuration. In addition, each asset provides the *Absolute Time* counter, which tracks elapsed time;
* Expected Lifetime: threshold value beyond which the activity is considered due;
* Subcritical Threshold: first threshold beyond which the activity is considered subcritical;
* Critical Threshold: threshold beyond which the activity is considered critical and must be performed soon;
* Translations: the counter’s name must be provided in all project languages. This name will be used to reference the counter across all pages.

<figure><img src="https://content.gitbook.com/content/pAbYPeH0IeVsC8b0gI87/blobs/lY0nMBhV7BlGLANZKPKh/2025-09-03%2012_06_17-Greenshot.png" alt=""><figcaption><p>Image C</p></figcaption></figure>

#### Associating Components and Siubgroups

<figure><img src="https://content.gitbook.com/content/pAbYPeH0IeVsC8b0gI87/blobs/FXyR1PKKW82YsTxxgzOD/2025-09-03%2012_06_29-Greenshot.png" alt=""><figcaption><p>Image D</p></figcaption></figure>

Once created, an activity can be associated with the objects on which it will be carried out, specifically components or entire subgroups. The *Select Components and Subgroups* button gives access to the view shown in Image E.

<figure><img src="https://content.gitbook.com/content/pAbYPeH0IeVsC8b0gI87/blobs/8RfqZiMaT8s9kZS3FXoi/2025-09-03%2012_06_48-Greenshot.png" alt=""><figcaption><p>Image E</p></figcaption></figure>

Here, you can choose the components and subgroups to associate with the activity. These represent the objects on which the activity will be executed when included in a maintenance record.

If a component is associated with an activity, only that object will be linked. If an entire subgroup is associated, all components currently included in it, as well as those added in the future, will automatically be associated with the activity.

#### Uploading Attachments

Each activity can have multiple attachments associated with it. The *Attachments* button in Image D opens the view shown in Image F. Here, all attachments related to the specific activity can be managed. In addition to adding or deleting files, you can also download a zip file containing all of them.

<figure><img src="https://content.gitbook.com/content/pAbYPeH0IeVsC8b0gI87/blobs/UOT2FHZrZAv5PSdfuwDo/2025-09-03%2012_07_24-Greenshot.png" alt=""><figcaption><p>Image F</p></figcaption></figure>

#### Excel Catalog Upload

To upload multiple activities at once, an Excel file can be used. The buttons highlighted in Image G allow you to either import an Excel file or download one containing the application’s current data.

For further information on the file structure and instructions on how to complete it, please refer to the [dedicated documentation](https://40factory.gitbook.io/mat-webapp-1/additional-mat-modules/maintenance/excel-catalogs).&#x20;
