One hierarchy, from portfolio to parking spot

Model every layer of your real estate — portfolio, property, building, floor, zone, and unit — in a single, relational structure that every module inherits automatically.

Unified portfolio hierarchy tree view showing portfolio, property, building, floor, zone, and unit levels

Interface preview

When buildings, floors, and units live in different systems, nothing reconciles

  • 1Property lists in one spreadsheet, unit rosters in another, and floor plans scattered across shared drives — no single source of truth.
  • 2Building managers cannot pull an accurate count of occupied units because the unit registry and lease system never reconcile.
  • 3Amenities and building systems are tracked in spreadsheets disconnected from the buildings they belong to, so bookings and maintenance miss context.
  • 4Adding a new floor or zone means updating multiple systems manually, and discrepancies compound with every change.
  • 5Reporting across the portfolio is impossible because each property uses a different taxonomy for floors, zones, and units.
The Solution

Arkan Unified Portfolio Hierarchy Capabilities

Six-level hierarchy, relationally enforced

Portfolio → Property → Building → Floor → Zone → Unit. Each level is a first-class entity with its own attributes, and child records inherit the parent context automatically.

Relational foreign keys enforce referential integrity — a unit cannot exist without a building, a zone cannot exist without a floor.

Properties that carry real attributes

Register properties with type (commercial, residential, mixed-use, industrial), latitude/longitude coordinates, total area, year built, tax ID, and descriptive metadata. Properties link upward to portfolios and downward to buildings.

Units with real status history

Track individual units — office, retail, residential, storage, parking, common area — with area, capacity, rent amount, currency, and a JSON status timeline capturing every transition between available, occupied, and under renovation.

Amenities and building systems, linked to place

Amenities (gyms, pools, meeting rooms) attach to buildings with capacity and operating hours and flow into the facility booking system. Building systems (HVAC, electrical, plumbing, fire safety, elevator, security) register with manufacturer details and service history and feed preventive maintenance scheduling.

Property contacts and directories

Maintain a per-property contact directory — owners, managers, emergency contacts, and maintenance personnel — with primary/secondary designation so the right person is always reachable in context.

Why Arkan?

Technical Comparison

See how Arkan outperforms traditional solutions

Feature
Arkan
Traditional
Hierarchy modeling
Six-level relational hierarchy with enforced foreign keys
Flat tables with building as a text field on unit records
Unit status tracking
JSON timeline capturing every status transition
Current status only — history lost on every change
Amenity integration
Amenities attached to buildings, flowing into facility booking
Amenities tracked in standalone spreadsheets
Building systems registry
Manufacturer, install date, service history feeding preventive maintenance
Disconnected equipment lists with no maintenance linkage
Key Performance Indicators

Dashboard KPIs

Total units across portfolio

Live count aggregated from the unit registry, scoped to the user's assigned buildings.

Buildings by type

Distribution of commercial, residential, mixed-use, and industrial buildings in the active portfolio.

Zones per floor

Average and maximum zone counts per floor, useful for identifying over- or under-segmented spaces.

How It Works

Simple 7-Step Process

1

Create a portfolio and attach one or more properties with their full attributes.

2

Register buildings under each property with code, type, floor count, total area, and year built.

3

Define floors with level numbers, total and usable area, and optional floor plan URLs.

4

Subdivide floors into zones with types and statuses for granular space management.

5

Register units under floors with type, area, capacity, rent, and currency.

6

Attach amenities and building systems to buildings; link contacts to properties.

7

Every downstream module — maintenance, leases, inspections, assets — inherits this hierarchy automatically.

Key Benefits

Measurable Impact

Hierarchy depth

6 levels

Portfolio, property, building, floor, zone, and unit — modeled as distinct entities, not flat tags.

Unit types supported

6 categories

Office, retail, residential, storage, parking, and common area — each with its own status lifecycle.

Property type coverage

4 classes

Commercial, residential, mixed-use, and industrial — one platform handles the full portfolio.

“Before ArkanPM, our unit count was a negotiation between three spreadsheets. Now the hierarchy is a single source of truth — every module references the same building, floor, and unit records.”

Portfolio Operations Lead

Portfolio Operations Lead

GCC Mixed-Use Portfolio

Industries Served

Built for Your Portfolio

Unified Portfolio Hierarchy supports property portfolios across every asset class

Commercial

  • Office towers with mixed tenant floors
  • Retail malls with anchor and in-line units
  • Business parks with multiple buildings

Residential

  • High-rise apartment buildings
  • Gated communities with villa clusters
  • Serviced apartment operators

Mixed-Use

  • Residential towers above retail podiums
  • Office and hotel combinations
  • Master-planned communities

Industrial

  • Logistics warehouses with loading zones
  • Light manufacturing facilities
  • Cold storage and distribution centers
Built For

Who Benefits

Tenant Admin

Gains a single registry of every property, building, and unit across the organization with consistent data definitions.

Facility Manager

Navigates from portfolio down to unit in one click, with every module reflecting the same hierarchy.

Building Manager

Sees only their assigned buildings with full hierarchy context — floors, zones, units, amenities, systems — in one view.

Owner

Sees the exact units they own within the correct building and floor context — no ambiguity about ownership scope.

Works seamlessly with other ArkanPM modules

Unified Portfolio Hierarchy integrates with Role-Based & Attribute-Based Access Control, Multi-Tenant Architecture, Role-Adaptive Dashboards and more for a complete property management platform.

Ready to Get Started with Unified Portfolio Hierarchy?

See how unified portfolio hierarchy can transform your property operations.

Bilingual EN / ARExpert implementationAll 16 modules

Related Features

Explore other features that work great with Unified Portfolio Hierarchy

Role-Based & Attribute-Based Access Control

Scope any user to specific buildings in the hierarchy with attribute-aware filtering.

Learn More

Multi-Tenant Architecture

Every portfolio is fully isolated at the database layer — tenants never see each other's hierarchies.

Learn More

Role-Adaptive Dashboards

Dashboard KPIs aggregate across the hierarchy and scope automatically by role.

Learn More