Projects - Intergraph Smart Completions - Intergraph Smart Completions Update 15 - Help - Hexagon

Intergraph Smart Completions Help (5.3.15)

Language
English
Product
Intergraph Smart Completions
Search by Category
Help
Smart Completions Version
5.3.15

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.