Local, Global and Reference Resources

There are three types of resources:  

  Local resources can be used only within the project in which they were created, and are therefore available only to users with permissions within that project.

  Reference resources (which are resources created in a reference project) can be used in any project throughout the database. However, in a secure database, they can be created and edited only by users who have the "Create/edit/delete local resources" permission within the reference project. These resources can be selected by any user who has at least the "Read" permission in the reference project. Users without permissions in the reference project can see the reference resources wherever they are used, but they will not be able to select or modify them.

  Global resources can be used in any project throughout the database. In a secure database, they can only be created and edited by users who have the “Create/edit/delete global resources” permission. However, they can be selected by any database user.

To make a resource global, select it in the Resource Manager and choose Home > Actions > Make Global.

Making a resource global cannot be undone and this option is not available for all resource types. If you make a resource global, any resources assigned to it will become global as well (e.g., if a URD has an assigned model, making that URD global will also make the model global, regardless of whether it was originally local or reference).

Parent/Child Resource Relationships

Certain resources can have other resources assigned to them (e.g., URDs can have models and tasks assigned to them, tasks can have models, crews and spare part pools assigned to them, etc.). This can be considered a "parent/child" relationship.

When you create a resource from within its parent, the child resource will be of the same type as its parent. For example, if you are working with a global URD and you add a model to it, the model will be global. If you are working with a reference task and you add a crew to it, the crew will be added to the reference project that contains the task.

When you assign existing resources to a parent resource, the following rules apply:

• Any resource assigned to a reference resource must be either a reference resource within the same project or a global resource (e.g., a local model cannot be assigned to a reference URD, nor can a model in "Reference Project 2" be assigned to a URD in "Reference Project 1").

• Any resource assigned to a global resource must be either a reference resource or a global resource (e.g., a local model cannot be assigned to a global URD).

Keeping Resources Together

The application will automatically keep copies of a project's resources and linked FMEAs when the project is restored, checked out, imported or exported.

• When you create a restore point, any reference resources, global resources or linked FMEAs used in the project are converted to local resources/FMEAs and stored with the backup.

• When you check out a project for local editing, any reference resources, global resources or linked FMEAs used in the project are converted to local resources/FMEAs and stored with the project.

• When importing/exporting a project item that uses reference resources, global resources or linked FMEAs:

• • If you import/export within the same database, the references will remain unchanged.

  • If you import/export between databases, the destination project will contain local copies of the original resources/FMEAs.

• When importing/exporting a project:

• • If you import/export a project that uses global resources, the destination project will contain local copies of the original resources.

  • If you import/export a project that uses reference resources or linked FMEAs:

  • • The references/FMEAs will be maintained if you also import/export the reference project at the same time.

    • If you don’t import/export the reference project at the same time, the new project will instead contain copies of the original resources/FMEAs.