On this page

In the Resource Usage Map application, you can detect three types of suspicious usages: inconsistent version usages, cyclic usages, and unused resources. In addition, you can filter and investigate suspicious usages by using the Filters pane. The sections below explain how to do that.

Inconsistent version usages

The inconsistent version usages filter allows you to see which resources use different versions of the same resource directly and through other used projects. You can investigate every inconsistent version usage displayed in your resource usage map as described below.


To investigate an inconsistent version usage

  1. In the Filters pane of a resource usage map, click  next to the inconsistent version usages filter to see the list of all the inconsistent version usages in the map.
  2. Select the inconsistent version usage you want to investigate. A detailed map of that usage is created in the content pane.
  3. Click the Details button on the top right corner of the inconsistent version usage map, to see full information of the selected usage as illustrated in the following figure.




As you can see in the example map below, Car Structure library directly uses version 20.0 of MD_customization_for_SysML but other resources used by Car Structure library use version 19.0 v9 of MD_customization_for_SysML (indirect usage).


An example of an inconsistent version usage map.

Cyclic usages

The cyclic usages filter allows you to see which resources use themselves through other used projects and form a usage loop. You can investigate every cyclic usage displayed in your resource usage map as described below.


To investigate a cyclic usage

  1. In the Filters pane of a resource usage map, click  next to the cyclic usages filter to see the list of all the cyclic usages in the map.
  2. Select the cyclic usage you want to investigate. A detailed map of that usage is created in the content pane.
  3. Click the Details button on the top right corner of the cyclic usage map, to see full information of the selected usage as illustrated in the following figure.



As you can see in the example map below, MD_customization_for_SysML uses itself by using ISO-80000 which uses QUDV_SysML 1.4 and QUDV_SysML 1.4 uses MD_customization_for_SysML thus forming a usage loop.


An example of a cyclic usage map.

Unused resources

The unused resources filter allows you to see which resources are not used by other resources stored in the Teamwork Cloud repository. This filter can only be displayed in a map created for all the resources in the repository.