🗺️ Dynamic Asset Navigation Overview

📷 Screenshot Placeholder

Image: dynamic-assets-navigation.png

Purpose Explain how uploaded asset types automatically become available as navigation items across the platform.

MapBilling uses a dynamic asset model, meaning the system automatically adapts based on the assets uploaded by an organisation.

Instead of having a fixed list of asset types, the platform creates asset management sections based on the organisation's actual infrastructure.

---

How Dynamic Assets Work

When an organisation uploads asset data, MapBilling identifies the asset type and automatically creates a corresponding navigation item.

Example:

Upload Asset File

        ↓

Asset Type Detected

        ↓

New Navigation Item Created

        ↓

Users Can Manage Asset Type

---

Example Workflow

Before Upload

The navigation may contain:

Operations

├── Dashboard
├── Map
├── Billing Points
├── Meter Reading
└── Customers

No infrastructure assets have been added yet.

---

Upload Pipeline Assets

Administrator uploads:

north-zone-pipes-july.svg

Asset Type:
Pipeline

The system processes the upload.

---

After Upload

The navigation automatically updates:

Operations

├── Dashboard
├── Map
├── Billing Points
├── Meter Reading
├── Customers
│
└── Assets
    └── Pipelines

Users can now access pipeline information.

---

Multiple Asset Types

Organisations can upload multiple asset categories.

Example:

Uploaded:

Pipelines

Meters

Valves

Reservoirs

Sensors

The navigation becomes:

Assets

├── Pipelines
├── Meters
├── Valves
├── Reservoirs
└── Sensors

---

Asset-Specific Views

Each generated asset menu provides a dedicated workspace.

Example:

Pipelines

Users can view:

• Pipeline map layer
• Pipeline attributes
• Material
• Diameter
• Condition
• Maintenance status

---

Valves

Users can view:

• Valve locations
• Valve type
• Operational status
• Maintenance history

---

Meters

Users can view:

• Meter location
• Customer connection
• Reading history
• Meter status

---

Map Integration

Dynamic assets automatically become map layers.

Example:

Map Layers

☑ Billing Points

☑ Customers

☑ Pipelines

☑ Valves

☑ Reservoirs

☑ Sensors

Users can:

• Turn layers on/off.
• Click assets.
• View details.
• Filter by attributes.

---

Asset Attributes Drive Behaviour

Assets are not limited to fixed fields.

Example:

Pipeline attributes:

Material:
HDPE

Diameter:
150mm

Pressure Zone:
North Ridge

Condition:
Operational

These attributes can be used for:

• Filtering
• Reporting
• Map visualisation
• Maintenance workflows

---

Dynamic Navigation Rules

The system automatically:

✅ Creates navigation items when new asset types are uploaded.

✅ Removes unused asset categories from the workspace.

✅ Links asset types to their map layers.

✅ Applies permissions based on user roles.

✅ Maintains asset history.

---

User Example

Scenario

A water company uploads a new set of reservoir sensors.

Before:

Assets

├── Meters
└── Pipes

After upload:

Assets

├── Meters
├── Pipes
└── Sensors

The operations team can immediately:

• View sensors on the map.
• Search sensors.
• Review sensor attributes.
• Monitor sensor status.

---

Why Dynamic Assets Matter

Traditional systems require developers to create new modules whenever a new asset type is introduced.

MapBilling allows organisations to expand naturally:

New Infrastructure

        ↓

Upload Data

        ↓

Asset Type Created

        ↓

Available To Operations Team

This makes the platform flexible as a water utility's infrastructure grows:

Meters
Pipes
Valves
Reservoirs
Sensors

---

Related Pages

• Asset Management
• Maps Overview
• Activity Log
• Reports