What are Instances and Projects - Intergraph Smart Completions - 5.3.6 - Help - Hexagon PPM

Smart Completions Help

PPMProduct
Intergraph Smart Completions
PPMCategory_custom
Help
version_completions
5.3.6

Depending on the project needs, Smart Completions allows System Administrators to create multiple Instances within a site and multiple projects within an Instance. There is no limitation to the number of Instances and Projects you can create. Some configurations and data are shared within Projects that are not shared between Instances, and each customer's specific circumstances will determine the logic employed.

The hierarchy is:

  1. First Level: Site. Some configuration changes will apply site-wide. These includes changes to the vResources and User Application.

  2. Second Level: Instance. An Instance is a grouping of projects. For Owner-Operators, this might be plant-based. EPCs might group all projects from a specific client into one Instance.

  3. Third Level: Project. A Project is defined by the scope of work. systemization, and handover/turnover packages necessary. You can assign the same asset to more than one project within an Instance. We assume assets and documents will be unique within the Instance.

Site-Wide Configurations:

  • Resource Manager: Anyone with access can assign users to any project, manage roles, and eliminate limiters. Only administrators should access this manager.

  • Projects: Anyone with a role granted the Manage right can assign projects and will be able to access All Projects from the project dropdown.

  • Roles and Role Profiles: While users are limited to Projects to which they are assigned, any assigned roles will apply to all of their Projects. It is not possible to have view-only rights in one Project and editing rights in a different Project.

  • Companies: similar to the description for Roles and Role Profiles.

  • In What is a User Application, adding roles to a manager and configuring rights will result in site-wide changes.

Instance Specific Configurations:

  • In What is a User Application, the Workflow Settings tab is Instance-Specific. Changes made here affect all Projects within the Instance. It’s important to note: changing the workflow settings in an active Project will cause corruption of existing data.

  • Switchboard Configurations.

  • Menu Configurations.

  • Disciplines apply to all Projects within an Instance.

  • Asset Types, Document Types, Punchlist Types, Punchlist Categories, and Table of Contents for handover packages.

  • Pack Types, Cable Types, Pipe Types, etc.

  • User Dashboard configurations, though users will be limited to data they are authorized to see.

  • Interface Labels.

Project Specific Configurations:

  • Assets and Tags. They can be assigned to more than one Project in an Instance, but it refers to the same record in the database.

  • Documents. Similar to assets.

  • What are Task Models, though they can be copied between Projects.

  • Systemization and Locations, though they can be copied.

  • Tasks exist only in a project, and they cannot be copied.

  • Certificate Types.

User Specific Configurations:

  • The Workspace tab is specific to each user. It can be copied from user to user.

  • Any Grid Layouts, changes to size of Columns. These can also be copied.

  • Limiters. These can also be copied.

  • Saved Searches. These can also be copied.

Using the Project Creation Wizard

The Project Creation Wizard creates new Projects and copies data from one Instance/Project to an existing Project. To access the wizard, click the New button from the bottom ribbon.

You can:

  • Create a Blank Project in the current Instance.

  • Copy data from an existing Project in the current Instance.

  • Copy data from an existing Project in a existing Instance.

  • Copy data from an existing Project in a new Instance.

  • Copy data from an existing Project to an existing Project.

  • Copy data from an existing Instance/Project into an existing Instance/Project.

The final option offers the most data to copy from one Project to another, so it may be worth creating the project first. The data that can be copied includes, but is not limited to the following:

  • Disciplines.

  • Dashboards.

  • Document Types.

  • Certificate Types.

  • Punchlist Types and Categories.

  • Task Models.

  • Task Model Headers.

  • Table of Content Definitions.

  • Systemization Tree.