> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Operations Levels in AssetOps

> Seamless navigation between portfolio and building levels

AssetOps provides flexibility in how you manage and administer maintenance operations, supporting both `portfolio-level` oversight and `building-level` execution. This dual-level approach allows you to coordinate strategies across your entire portfolio while addressing the specific needs of individual buildings.

Actions and configurations applied at the portfolio level determine the availability or configuration of resources at the building level. Subsequently, actions performed at the building level are reflected at the portfolio level, ensuring centralized visibility and consistent management across all sites.

```mermaid actions={false} theme={null}
---
config:
  layout: dagre
  theme: neutral
---
flowchart TD
 subgraph s1["Operation Levels"]
        A1["Portfolio-Level"]
        A2["Building-Level"]
  end
 subgraph s2["Buildings"]
        B1["Building 1"]
        B2["Building 2"]
        B3["Building 3"]
  end
    A["AssetOps"] -- access --- A1
    A1 -- access --- A2
    A2 -- access --- B1 & B2 & B3
    s2 -- perform --- P["Building-Level Ops"]
    P -- reflect back --- A1
    A1 ---|perform| A3
    A3 -- determine --- P
        A3["Portfolio-Level Ops"]

     A1:::Sky
     A2:::Sky
     B1:::Rose
     B2:::Rose
     B3:::Rose
    classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
    classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
    linkStyle 0 stroke:#00C853,fill:none
    linkStyle 1 stroke:#00C853,fill:none
    linkStyle 2 stroke:#FF6D00,fill:none
    linkStyle 3 stroke:#FF6D00,fill:none
    linkStyle 4 stroke:#FF6D00,fill:none
    linkStyle 5 stroke:#FF6D00,fill:none
    linkStyle 6 stroke:#00C853,fill:none
    linkStyle 7 stroke:#FF6D00,fill:none
    linkStyle 8 stroke:#FF6D00
```

## Portfolio-Level

The portfolio level in AssetOps provides centralized oversight of all buildings for a client, serving as the main management hub. From this level, you can initially manage and monitor the entire portfolio, while also using it as the entry point to access and manage individual buildings.

In addition, the portfolio level allows configuration of portfolio-wide settings and the management of shared resources, such as vendors, categories, or task templates, ensuring consistent operations and standardized processes across all sites.

```mermaid actions={false} theme={null}
---
config:
  theme: neutral
---
flowchart LR
 subgraph s1["Portfolio Buildings"]
        N1["Building 1"]
        N2["Building 2"]
        N3["Building 3"]
  end
 subgraph s2["Portfolio-Level Ops"]
        B1["Analytics"]
        B2["Buildings"]
        B3["Work Orders"]
        B8["Schedules"]
        B4["Vendors"]
        B5["Categories"]
        B9["Templates"]
        B6["Settings"]
  end
    A["AssetOps"] -..- B["Portfolio-Level"]
    B ---- B1 & B2 & B3 & B8 & B4 & B5 & B9 & B6
    B2 -- "access building-level" ---- N1 & N2 & N3

     N1:::Sky
     N2:::Sky
     N3:::Sky
    classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
    linkStyle 1 stroke:#00C853,fill:none
    linkStyle 2 stroke:#00C853,fill:none
    linkStyle 3 stroke:#00C853,fill:none
    linkStyle 4 stroke:#00C853,fill:none
    linkStyle 5 stroke:#00C853,fill:none
    linkStyle 6 stroke:#00C853,fill:none
    linkStyle 7 stroke:#00C853,fill:none
    linkStyle 8 stroke:#00C853
    linkStyle 9 stroke:#FF6D00,fill:none
    linkStyle 10 stroke:#FF6D00,fill:none
    linkStyle 11 stroke:#FF6D00,fill:none
```

## Building-Level

At the building level, AssetOps allows you to manage operations for a specific building in detail. You can add and manage assets, create and track work orders, and apply configuration policies defined at the portfolio level.

Building-level operations also include allocating work through routing and dispatch, managing teams, and overseeing day-to-day maintenance activities. All actions performed at the building level flow back to the portfolio level, ensuring complete visibility and consistent oversight across the entire portfolio.

```mermaid actions={false} theme={null}
---
config:
  theme: neutral
---
flowchart LR
 subgraph s1["Portfolio Buildings"]
        N1["Building 1"]
        N2["Building 2"]
        N3["Building 3"]
  end
 subgraph s2["Building-Level Ops"]
        A["Analytics"]
        B["Work Orders"]
        C["Schedules"]
        D["Assets"]
        D1["Asset Discovery"]
        E["Teams"]
        F["Routing & Dispatch"]
        G["Completion Policies"]
  end
    N2 -- "building-specific" ----- A & B & C & D & D1 & E & F & G
    O["AssetOps"] -..- O1 ---|access| N2
O1[Building-Level] 
     N1:::Sky
     N2:::Sky
     N3:::Sky
    classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
    linkStyle 0 stroke:#FF6D00,fill:none
    linkStyle 1 stroke:#FF6D00,fill:none
    linkStyle 2 stroke:#FF6D00,fill:none
    linkStyle 3 stroke:#FF6D00
    linkStyle 4 stroke:#FF6D00,fill:none
    linkStyle 5 stroke:#FF6D00,fill:none
    linkStyle 6 stroke:#FF6D00,fill:none
    linkStyle 7 stroke:#FF6D00,fill:none
```

## Role-Based Access Implications

Your [role in KODE OS](/products/launchpad/client-organizations/apps/#kode-os-roles) determines whether AssetOps is available to you and, if so, defines your specific permissions within the product.

Understanding role-based permissions is essential, as they govern what actions you can perform, which assets and buildings you can access, and how you interact with AssetOps overall.

Creating distinct KODE OS roles for AssetOps can be highly beneficial, allowing you to allocate appropriate levels of access to different users based on their responsibilities.

This approach ensures that users have the tools and visibility they need to perform their tasks efficiently, while control, security, and consistent operational standards are preserved across the organization.
