.png?width=250&height=54&name=ORIS%20logo%20Horizontal%20Colours%20(1).png)
ORIS Platform Structure: Workspaces, Assets, and Access
How ORIS organises projects, controls access, and structures the assets that power your projects.
Construction Operation Libraries
Organisation
The Organisation is the top level of the ORIS hierarchy. It represents your company and is shared by all users within it. Shared settings, and custom material databases configured for your team are all available at this level.
Click your profile icon (top-right corner) to open the account menu, where you can see your current organisation, and other organisations you are part of. From there, you can see all available Organisations and switch between them by double-clicking the one you want to access.
Tip
When you first log in, your account may be associated with both a personal organisation and your company Organisation. Always work from the company Organisation: Workspaces and assets created here are accessible to colleagues, whereas those created in a personal organisation are not.
Workspaces
Within an Organisation, work is divided into Workspaces. A workspace is a project container: it holds all the assets associated with a given project and controls who on the team can access them. Each workspace has its own user list, and team members can be invited with different permission levels.
A workspace typically represents one project, though teams are free to organise by client, region, or any other structure that suits their workflow. All workspace assets, including material assessments, private production sites, and portfolios, are visible to anyone with access to that workspace.
Go to the homepage and use the workspace selector in the left sidebar to choose the workspace you want to work in. Next to it, the three-dots icon provides access to the full list of workspaces you belong to, where you can also create a new one. Alternatively, you can use the New workspace button in the central homepage panel to access the same workspace list and creation options. From there you can see the full list of assets on each workspace, and you can also manage users' access:
- Admin: Has full control over the workspace. Can manage users, update roles, and delete the workspace. To leave, another admin must exist, or assets must be transferred.
- Manager: Can manage team members except an admin. To leave, owned assets must be transferred.
- Member: Can view the team list. To leave, owned assets must be transferred.
Tip
Keep all Material Assessments, Private Production Sites, and Project Portfolios for the same project in the same workspace. Both the Comparison Dashboards and the Project Portfolios draw only from the active workspace, so splitting a project across workspaces will prevent these features from working as intended.
Assets Inside a Workspace
Three types of assets can be created within a workspace: Material Assessments, Private Production Sites, and Project Portfolios. To access existing assets or create new ones, go to the homepage and use the workspace selector in the left sidebar to choose the relevant workspace. Then select the relevant asset type from the list below to view existing assets or create new ones.
MATERIAL ASSESSMENTS
A Material Assessment evaluates project KPIs such as the carbon footprint, cost and material consumption of a project or a defined part of one. It is the primary asset in ORIS, and its scope can be defined in three different ways depending on the project structure.
Full project
A single assessment covers the entire project scope. Suitable for straightforward projects with a unified bill of quantities.
Section or group of elements
For complex projects, separate assessments can be created for each section, structure, or element group. A Project Portfolio then combines them into a single project-level view.
Design scenario or option
An assessment can represent a design alternative or material scenario. All assessments in the same workspace are then available in the Comparison Dashboard for side-by-side analysis.
PRIVATE PRODUCTION SITES
ORIS includes a public database of production sites and waste facilities. Private Production Sites extend these capabilities with project-specific or confidential sourcing data: for example, a recycled aggregate stockpile on an adjacent site, or a mobile asphalt plant. They are only visible within the workspace they belong to.
Important
A Private Production Site will only appear in site selection results if its site type matches the site type filter set for the corresponding material in the Material Assessment, and if it belongs to the same workspace.
PROJECT PORTFOLIOS
A Project Portfolio groups multiple Material Assessments into a unified dashboard showing combined results of both cost and carbon footprint, as well as the individual contribution of each assessment. It is designed for projects where the scope has been divided across several Material Assessments, whether by section, structure, or work packages.
Portfolios can also be compared against each other using the same Comparison Dashboard available for individual Material Assessments, making it possible to evaluate whole-project alternatives side by side.
Important
All assessments included in a portfolio must use the same currency.
Construction Operation Libraries
In addition to workspace assets, ORIS enables users to create custom libraries of construction operations that define equipment, personnel, and activities associated with material handling and installation. To access an existing library of operations, or to create a new one, go to the homepage and select My Libraries, located at the bottom-left of the sidebar.
Libraries can be configured to reflect specific project types, such as bridge or rail works, and may include equipment definitions, personnel rates, and construction operations composed of both.
Resources can be created from scratch or imported from existing libraries, including the ORIS default library (focused on road and pavement engineering), to improve efficiency and maintain consistency.
When creating a library, users must select whether it is saved at the organisation level, making it accessible to all users within the organisation, or at the personal level, where it remains accessible only to the creating user. Organization-level libraries are intended for standardised or frequently reused operation sets, while personal libraries are suited to individual or project-specific use.