Right People. Right Tasks. Right Time.
Optimize workforce efficiency with Omega 365 Resource Management. From planning and assigning resources to tracking availability and skills, this module keeps projects aligned and teams empowered.
Request a demo
Plan and monitor resource assignments; track availability, skills, and workloads to optimize team utilization across projects.
Key Features
Resource Register
Position Management
Integration
Benefits
Efficiency
Streamline planning and allocation processes
Visibility
Gain a real-time overview of resource use
Control
Support accurate forecasting and cost management
Create Org Unit
Organizational Units (Org Units) are the fundamental building blocks of the organizational structure in Omega 365. They are used to represent entities such as departments, projects, contracts or operational units, organized in a hierarchical structure.
Org Units define ownership, access control, data separation and visibility across the system. A well-structured Org Unit hierarchy is therefore essential for successful Completion setup and execution.
Org Units are used in the material management module in Omega 365 to establish warehouses, projects, assets and legal entities.
Org Units are created in the Org Units application by clicking New.
Org Unit Fields
When creating an Org Unit, the following fields are available:
Name | Mandatory. Internal name used to identify the Org Unit in the hierarchy. |
Title | Mandatory. Display name shown to users. |
Unit Type | Drop-down menu, most commonly Project or Contract. The Unit Type helps categorize the Org Unit and may influence behavior in other parts of the system. |
Name Prefix | Prefix added to the Org Unit name, typically used to enforce naming conventions. |
Parent (Belongs To) | Defines the parent Org Unit in the hierarchy. This relationship controls inheritance of access, roles and visibility. |
Company | Selects which company the Org Unit represents. Values are retrieved from the System Companies application. |
Responsible | Identifies the person responsible for the Org Unit. |
External Org Unit Reference | Optional reference used for integration or mapping to external systems. |
Color | Used in Board Plan views to visually distinguish Org Units. |
Planned End Date | Optional date indicating the planned end of the Org Unit. |
Closed | Date and time indicating when the Org Unit was closed. |
Org Unit Options (Checkboxes)
Do not inherit roles / access | Prevents the Org Unit from inheriting roles and access rights from its parent Org Unit. |
Exclude from resource management | Excludes the Org Unit from being used in the Resource Management module. |
Is Operation | Indicates that the Org Unit represents an operational context rather than a project execution context. This option is typically used for asset operations and lifecycle follow-up after handover. Its usage depends on organizational setup and should be clarified during implementation. |
Domain
A Domain is used to group multiple Org Units in order to control data sharing, object visibility and object uniqueness.
By clicking Set as Domain, the current Org Unit is defined as a Domain. While Domains are most commonly defined at project level, they may also be applied at other levels depending on organizational and data-sharing requirements.
When an Org Unit is part of a Domain:
objects within the Domain hierarchy are visible across all Org Units in that Domain,
object uniqueness is enforced across the Domain,
key Completion applications such as Scope Explorer, Object Explorer and Object Importing rely on the Domain structure to function correctly.
Object uniqueness within a Domain is defined by the combination of:
Object Name
Object Type
Domain
The Domain to which an Org Unit belongs is displayed under the Org Unit title as:
The Domain to which an Org Unit belongs is displayed under the Org Unit title as:
Domain: [Domain Name]
Get to Know Your Product Manager
Audun Habbestad
Audun Habbestad is based in Ølensvåg, Norway, and joined Omega 365 in 2005. He has worked with several major clients, and his expertise spans technical information management, document control, and lifecycle information, particularly in operations and modification projects. Throughout his career, Habbestad has maintained close client relationships, delivering tailored solutions for complex needs.
Contact Us – We’re Here to Help!
If you’re interested in learning more about Omega 365’s solutions or would like additional information, feel free to reach out to us.