InfraLink provides a flexible and secure framework for managing multiple projects and/or teams using a single instance of the software. InfraLink Contracts act as security containers for partitioning work data. While Contract-specific data is fully isolated, certain InfraLink configurations occur at the instance level, or globally. It is important to keep these global configurations under consideration when planning and managing InfraLink deployments.

Instance Ownership

While InfraLink is designed to support a range of projects within a single Instance, the design of the underlying data model, as well as its security implications, is based on a general assumption that an InfraLink Instance has a single point of ownership. That is, while multiple teams or organizations may utilize the instance, it is recommended that an InfraLink Instance follow one of the following two common deployment scenarios:

• Infrastructure Owner-Managed Instance: The owner of the infrastructure/system(s) under maintenance, or its representative (e.g., PMO), deploys InfraLink to manage the work of one or multiple contractors. The instance owner appoints the administrator(s) responsible for the global management of the instance, to ensure configuration consistency and data integrity across the project(s).
• Contractor-Managed Instance: A contractor deploys InfraLink to manage the services it provides to one or multiple infrastructure owner(s). The contractor defines and manages projects (i.e., contracts) specific to the infrastructure/systems(s) and work scopes associated with each infrastructure owner. The Contractor appoints the administrator(s) responsible for the global management of the instance, to ensure configuration consistency and data integrity across the project(s).

Instance Administrator

Regardless of the Instance ownership scenario, an Instance Administrator is responsible for the creation and management of all Instance-level (i.e., global) configurations and definitions. An Instance Administrator is granted global Permissions for this purpose and will ensure that:

• User Accounts are properly validated and the appropriate Roles are assigned;
• instance-level definitions are created, as needed, to support each Contract managed under the Instance; and
• global definitions and configurations are associated with only the appropriate Contracts.

As new Contracts are created under an existing Instance, the Instance Administrator will ultimately determine if existing global definitions can be shared with the new Contract or new definitions must be created.