All work

KangaVault

KangaVault

KangaSys

Building Intelligence & Sustainability Platform · Australia

KangaVault — Building Intelligence & Sustainability Platform

Making fragmented building-system data accessible for sustainability.

  • Building Intelligence
  • Sustainability
  • Energy Monitoring
  • Enterprise UX
  • UX Architecture

How do you make a complex building intelligence platform usable for the people responsible for running a hotel?

Hotels and commercial buildings generate operational data across meters, sensors, floors, rooms, equipment, and people. But collecting that data is only part of the challenge. Teams need to configure the building, connect devices, manage records, understand operational conditions, and turn fragmented information into something they can act on.

KangaVault / KangaSys is a building intelligence and sustainability platform designed for an Australian context, bringing building infrastructure, energy consumption, occupancy, and operational information into a more connected experience.

My work focused on simplifying the configuration and management experience, particularly for users with different levels of technical expertise. This meant thinking beyond individual screens to understand how buildings, floors, meters, sub-meters, rooms, devices, and operational users relate to one another.

The goal was to make a technically complex system easier to configure, navigate, and maintain.

Product
KangaVault / KangaSys
Domain
Building intelligence and sustainability
Primary context
Hotels and commercial buildings in Australia
My focus
UX/UI design, onboarding, configuration, information architecture, and operational workflows
Key workflows
Building setup, sensor connectivity, building hierarchy, CRM and records management, employee information, and floor-supervisor workflows
Collaboration
Product and engineering stakeholders
01 — The context

Buildings generate data. People need decisions.

A hotel is a complex operating environment. Guest rooms, kitchens, laundries, restaurants, conference facilities, lifts, heating and cooling systems, lighting, and back-of-house areas all contribute to the building’s operational footprint.

For facility and sustainability teams, understanding the building requires more than viewing a single energy-consumption figure. They need to understand where the data originates, which part of the building it represents, how it changes over time, and who is responsible for acting on it.

A building intelligence platform can help connect these operational layers.

  1. 1

    Building and floor hierarchies

    Provide the context for locating equipment and consumption data.

  2. 2

    Meters and sub-meters

    Help associate energy usage with relevant parts of a property.

  3. 3

    Sensors and connected devices

    Provide operational observations, depending on the installed hardware.

  4. 4

    Employee and supervisor records

    Help identify the people associated with operational responsibilities.

  5. 5

    Centralised records

    Help teams maintain information about properties, equipment, and their associated users.

The UX challenge is to make these relationships understandable without requiring every user to understand the underlying technical architecture.

Why NABERS is important

NABERS, the National Australian Built Environment Rating System, provides independent ratings of building performance. For hotels, it offers a framework to assess energy efficiency and water efficiency, alongside separate waste-verification and carbon-neutral certification pathways.

A NABERS hotel rating uses 12 months of operational data and compares the building’s performance against an industry benchmark. The energy rating is expressed on a six-star scale, with three stars representing average performance and six stars representing market-leading performance.

  1. 1 stars
  2. 2 stars
  3. 3 stars
  4. 4 stars
  5. 5 stars
  6. 6 stars
3 stars: average6 stars: market-leading

Operational efficiency

Understand energy consumption and identify opportunities to reduce operating costs.

Performance benchmarking

Compare a hotel’s performance against relevant industry benchmarks.

Investment decisions

Use operational evidence to inform building upgrades and efficiency initiatives.

Sustainability communication

Demonstrate environmental performance to stakeholders and prospective customers.

Portfolio oversight

Compare properties and identify where further investigation or improvement may be worthwhile.
01 / 05

These are important reasons for reliable building data and usable monitoring tools. A software platform can support data collection, organisation, and analysis, but the official NABERS rating itself requires an accredited assessor and compliant evidence.

The product opportunity

Make the building and its operational data easier to configure and understand, so teams can spend less effort navigating disconnected information and more effort improving performance.

02 — The UX problem

Complexity begins before the dashboard

A common assumption with operational software is that the dashboard is the main experience. In reality, its usefulness depends on the quality of everything that comes before it.

Before a hotel team can make sense of building information, the system needs a meaningful structure. Properties must be represented correctly. Floors and rooms need to be associated with the right building. Meters and other devices need to be mapped to the relevant locations or equipment. Operational records need to be maintained.

If these relationships are difficult to establish or understand, even a well-designed dashboard can become difficult to trust and use.

  1. Area 1

    Setup and configuration

    Users need to establish the building structure and configure the system before they can make effective use of the information it contains.

  2. Area 2

    Hardware and data connectivity

    Technical users need to connect and configure sensors, meters, and endpoints, while non-technical users need to understand their status and identify when something requires attention.

  3. Area 3

    Operational records

    Property information, employee records, and supervisor responsibilities need to be organised so that users can find the information relevant to their work.

  4. Area 4

    Monitoring and interpretation

    Building and energy data needs to be presented with enough context for users to understand what it represents and what to investigate next.

These are not independent screens. They form a connected operational experience.

03 — Building setup experience

From an empty system to a configured building

The initial setup experience establishes the foundation for everything that follows. Users need a way to represent the real-world building inside the software before they can meaningfully associate devices, operational information, and consumption data with it.
Building hierarchy
  1. Property
  2. Building
  3. Floor
  4. Room or area
  5. Meter, sub-meter, or device

The exact hierarchy depends on the property’s infrastructure and the product’s supported configuration.

A building is easy to understand physically, but its digital representation can become complicated. Some users think in terms of floors and rooms; others think in terms of meters, endpoints, electrical circuits, or building systems.

The interface needs to support both ways of thinking.

Design considerations

  • Establish a clear hierarchy

    Make the relationship between properties, buildings, floors, rooms, and devices visible. Users should understand where an item belongs and how it relates to the larger property.

  • Separate essential information from technical configuration

    Collect the information needed to establish the building first, then provide access to more advanced configuration when required.

  • Make relationships explicit

    When users create or edit a floor, room, meter, or device, clearly identify its parent building or area. This reduces the risk of associating data with the wrong location.

  • Support ongoing changes

    Buildings evolve. Equipment is replaced, rooms are repurposed, and monitoring requirements change. Configuration should support maintenance without forcing users to reconstruct the entire property.

  • Make setup status understandable

    Where the product supports it, communicate which setup steps are complete, which items remain unconfigured, and what needs attention before the system can be used effectively.

The design principle

Treat building configuration as the creation of a reliable digital representation of a real-world property, not simply a form-filling exercise.

04 — Sensor connection and device configuration

Connecting the physical building to the digital system

Building intelligence depends on information coming from physical infrastructure. Meters, sub-meters, sensors, and other endpoints may provide data relating to energy consumption, occupancy, or other operational conditions, depending on the hardware deployed.

Connecting these components introduces a different level of complexity from managing ordinary business records.

Technical users may need to configure device identifiers, communication settings, or connection parameters. Operational users may only need to know which device belongs to a location, whether it is connected, and whether its data is available.

The UX needs to support both audiences without making every user navigate the same technical details.

Three states, not one
  1. Configured
  2. Connected
  3. Providing data

A configured device is not necessarily connected, and a connected device is not necessarily providing usable data.

Key workflow considerations

  • Device registration

    Give users a clear way to add a device and identify it within the building’s hierarchy.

  • Location and asset mapping

    Associate the device with the correct building, floor, room, meter, or equipment where applicable.

  • Connection status

    Distinguish between a device that has been configured, one that is connected, and one that is actively providing usable data. These states should not be treated as interchangeable.

  • Error recovery

    Where connection failures or missing data occur, provide understandable status information and a clear next step rather than exposing only technical errors.

  • Device maintenance

    Support changes to device assignments and configurations as the physical building evolves.

Designing for mixed technical abilities

For a networking or engineering user, configuration details may be necessary. For a floor supervisor, those same details may be unnecessary and confusing.

A better experience presents the information relevant to each user’s task while preserving access to deeper technical details for those who need them.

The design principle

Make the technical state of a device understandable without requiring every user to understand the technology behind it.

05 — CRM and property information

Bringing operational records into context

Building intelligence is not only about sensors and energy readings. It also depends on having an organised record of the properties and operational entities represented in the system.

In a hotel or commercial-building environment, users may need to maintain property details, building information, associated records, and the relationships between them.

The CRM or management component of the product should help users establish a dependable source of operational information rather than forcing them to reconstruct context across disconnected records.

The UX challenge

Information becomes difficult to manage when similar records are duplicated, relationships are unclear, or users cannot easily identify which property, building, or team a record belongs to.

The challenge is to make records easy to locate, maintain, and associate with the correct operational context.

Structured records

Present property and related information in predictable formats so users can scan, review, and update it consistently.

Clear relationships

Make it apparent which building or property a record belongs to and how associated information connects to it.

Useful search and filtering

Help users find the relevant record when working across multiple properties, buildings, floors, or operational entities.

Controlled editing

Where roles and permissions apply, make it clear who can create, update, or manage different records.

Consistency across the platform

Reuse familiar patterns for viewing, creating, editing, and reviewing records rather than introducing a different interaction model for every module.
01 / 05
The design principle

Treat record management as part of the operational system, not as a disconnected administrative module.

06 — Employee and floor-supervisor records

Connecting people with the places they manage

Operational software becomes more useful when it reflects the people responsible for maintaining and running the building.

Employee records and floor-supervisor information introduce a people-management layer into the wider building intelligence experience. These records may help users understand who is associated with a property, who supervises a particular area, and where operational responsibilities sit.

The exact relationships depend on the product’s implemented functionality.

Employee records

Employee information needs to be organised so that authorised users can find the right record and understand its relevance to the organisation or property.

  • Clear identification and readable employee details.
  • Association with the appropriate property, team, or operational unit.
  • Consistent creation, editing, and record-review patterns.
  • Clear handling of required information and incomplete records.
  • Role-appropriate access to employee information.

Because employee records contain personal information, the interface should expose only the information necessary for each user’s responsibilities.

Floor-supervisor information

Floor supervisors occupy an important position between building operations and day-to-day activity. Their information needs to be accessible in the context of the floors or areas they oversee, where the product supports those associations.

  • Which floor or area a supervisor is associated with.
  • Which building or property that area belongs to.
  • What supervisory information is available in the system.
  • How authorised users can update assignments when responsibilities change.

If the system supports assigning supervisors to floors, the relationship should be explicit and easy to review. Users should not have to infer responsibility from disconnected employee and floor records.

The UX opportunity

By organising people and building information around meaningful relationships, the product can reduce the effort required to understand who is associated with a location and where relevant operational information can be found.

07 — Building data for hotel operations

From raw information to operational understanding

Once the property structure, device relationships, and supporting records are configured, the next challenge is presenting building information in a form that people can understand.

For hotel operators, the value of energy monitoring lies not simply in collecting readings, but in understanding consumption and identifying opportunities for improvement.

A well-structured monitoring experience should help users connect a reading to its source, location, time period, and relevant operational context.

Information that matters

  • Energy consumption

    Show consumption information with meaningful units, time periods, and building context.

  • Location-based monitoring

    Where metering supports it, help users compare consumption across buildings, floors, or areas.

  • Data availability

    Make missing, stale, or unavailable readings distinguishable from genuine zero consumption.

  • Historical comparisons

    Where historical data is available, enable users to understand changes over time and investigate unusual patterns.

  • Operational follow-up

    Help users identify where additional investigation may be necessary without implying that a dashboard alone can diagnose the underlying cause.

Connecting the product to NABERS

NABERS provides a standardised way to assess building performance using operational data and appropriate benchmarks. KangaVault / KangaSys can be positioned in this broader context as a building intelligence platform that helps organise and understand the operational information relevant to energy management.

The distinction matters: monitoring software can help teams collect, interpret, and act on building data, while an official NABERS rating involves its own methodology, evidence requirements, and accredited assessment process.

The design principle

Give every important data point enough context to answer three questions:

  1. 01

    Where did it come from?

  2. 02

    What does it represent?

  3. 03

    What should the user investigate next?

08 — Two very different audiences

One platform, different levels of technical confidence

A key design consideration was the range of users interacting with the system.

A technical user configuring meters or devices may need precise configuration information and a clear view of system relationships. A hotel operations user may be more interested in locating a floor, checking information, reviewing records, or understanding whether a device is functioning as expected.

An experience designed exclusively for technical users risks making routine tasks unnecessarily difficult for operational teams. An experience designed exclusively for non-technical users risks hiding the controls required to configure and maintain the system.

For technical users

  • Expose relevant configuration details.
  • Make device and building relationships clear.
  • Provide meaningful status and troubleshooting information.
  • Preserve access to advanced settings where needed.

For operational users

  • Use familiar language for buildings, floors, rooms, and records.
  • Keep common tasks easy to locate.
  • Communicate system status in understandable terms.
  • Avoid exposing technical details unless they help the task at hand.

Across both audiences

  • Use consistent terminology.
  • Maintain predictable interaction patterns.
  • Provide clear feedback after changes.
  • Make the consequences of configuration actions understandable.

The goal is not to remove complexity from the underlying system. It is to present that complexity at the right level for the user and task.

09 — My approach

Designing around relationships

My work on KangaVault / KangaSys involved thinking through how users configure and interact with a building intelligence system whose information spans physical infrastructure, connected devices, and operational records.

Rather than treating onboarding, device configuration, and information management as isolated screens, the experience needed to reflect the relationships between them.

Understanding the underlying data model

Working with engineering to understand backend structures and technical constraints helped establish how buildings, floors, meters, sub-meters, rooms, and endpoints related to one another. This was important for defining which relationships users needed to see and how configuration should be represented in the interface.

Simplifying configuration

The setup experience needed to support users with different levels of technical knowledge. The focus was on making configuration understandable, organising information into meaningful groups, and preserving access to technical details where required.

Establishing consistent interaction patterns

Building setup, device management, and record maintenance share common needs: users must identify an entity, understand its context, make a change, and know whether that change was successful. Consistent patterns reduce what users need to learn as they move through the product.

Connecting interface decisions to technical constraints

In a data-heavy product, interface design cannot be separated from the way information is represented and delivered by the underlying system. Understanding those constraints helps avoid designs that are visually clear but difficult to implement or maintain.
01 / 04
10 — What this project demonstrates

Enterprise UX for the physical world

KangaVault / KangaSys represents a different side of enterprise UX from conventional SaaS dashboards. The experience has to connect the physical structure of a building with its data, devices, and operational users.

The core design challenge is relational: a meter belongs somewhere, a sensor represents something, a floor exists within a property, and a supervisor may be responsible for a specific area. When those relationships are difficult to understand, the entire system becomes harder to use.

  • Systems thinking

    Understanding how building entities and operational workflows connect.

  • Configuration UX

    Making technical setup manageable for different user groups.

  • Information architecture

    Giving complex building data a clear and navigable structure.

  • Cross-functional collaboration

    Aligning the user experience with backend models and technical constraints.

  • Sustainability context

    Understanding why reliable building data matters to energy monitoring and performance improvement.

Closing thought
Good building intelligence starts before the dashboard. It starts with making the building, its devices, its data, and the people responsible for it understandable as one connected system.

That is the UX opportunity behind KangaVault / KangaSys: turning technical building infrastructure into an experience that people can configure, navigate, and use with confidence.

Information architecture

How the product is structured — the top-level areas and what lives inside each.

KangaVault
  • Portfolio
    • Buildings
    • Floors
    • Rooms
  • Metering
    • Meters
    • Sub-meters
    • Hierarchy
  • Setup
    • Onboarding
    • Data sources
    • Mapping
  • Insights
    • Energy
    • Occupancy
    • Efficiency
  • Reporting
    • NABERS
    • Exports

Wireframes

Low-fidelity layouts for the key screens, focused on structure and hierarchy before visual design.

Building setupGuided onboarding that structures buildings, floors and meters.
Energy insightsConsumption and occupancy trends understandable by non-engineers.