> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/data-and-reporting/analytics-pro/dashboard/ambient-noise-and-sound.md).

# Ambient Noise & Sound 🔈

<figure><img src="/files/W3Kgl6nnBvMPvP7GNS7P" alt=""><figcaption></figcaption></figure>

### Overview

The Ambient Noise and Sound Level dashboard tracks acoustic conditions across the workplace. It captures both **ambient noise** (background level, useful for baseline workplace acoustics) and **sound level** (peak event-driven noise), each measured in decibels.

Use this dashboard to:

* Identify noise hotspots and quiet zones
* Inform open-plan and neighbourhood-design decisions
* Validate the acoustic performance of meeting rooms and breakout spaces
* Provide objective data to support flexible-working and focus-area policies

***

### Sensor Status Bands

The dashboard uses the following status bands for both Ambient Noise and Sound Level readings:

| Status        | Range    | Meaning                                                        |
| ------------- | -------- | -------------------------------------------------------------- |
| 🟢 Excellent  | < 40 dB  | Very quiet; ideal for focused work                             |
| 🟡 Acceptable | 40–50 dB | Moderate background noise; typical open office                 |
| 🔴 Poor       | ≥ 50 dB  | High noise level; likely to impact concentration and wellbeing |

#### Acoustic Reference (General Guide)

| Level      | Range    | Typical Environment                           |
| ---------- | -------- | --------------------------------------------- |
| Very Quiet | < 40 dB  | Library, private office, focus zone           |
| Moderate   | 40–50 dB | Open office hum, normal conversation          |
| Loud       | 50–65 dB | Busy café, multiple overlapping conversations |
| Disruptive | > 65 dB  | Noisy environment; fatigue rises rapidly      |

***

### Dashboard Structure

The dashboard is organised into four tabs:

1. **Monitoring**
2. **Data**
3. **Map**
4. **Floor Heatmap**

A metric switcher toggles every chart between **Ambient Noise** and **Sound Level**.

***

### Tab 1 — Monitoring

#### Ambient Noise Trend

<figure><img src="/files/AQWL1xPnmBJGr2GkQeHH" alt=""><figcaption></figcaption></figure>

*Line chart with Daily / Weekly granularity tabs.*

Ambient noise level (dB) over time. Background bands mark the Quiet / Active / Loud / Disruptive zones.

*Use it to:* track whether the workplace is becoming louder over time — a common pattern as desk density rises.

#### Average Ambient Noise by Resource

<figure><img src="/files/pAS1fhpzXjOMboB509sG" alt=""><figcaption></figcaption></figure>

*Horizontal bar chart, ranked.*

Resources ranked by ambient noise, colour-coded by band.

*Use it to:* identify the loudest neighbourhoods and the quietest, supporting the assignment of focus and collaboration zones.

#### Average Ambient Noise by Weekday

<figure><img src="/files/m2FeOKZ4UXxCWfqyoc8i" alt=""><figcaption></figcaption></figure>

*Bar chart.*

Noise averages by day of the week.

#### Sound Level Trend

<figure><img src="/files/gLLXu1IORbRhpyt1cKlw" alt=""><figcaption></figcaption></figure>

*Line chart with Daily / Weekly granularity tabs.*

Peak sound level (dB) over time, with reference threshold lines.

*Use it to:* detect transient noise events such as construction, equipment startup, or alarms.

#### Average Sound Level by Resource

<figure><img src="/files/CZPJ84KIoYX8B6nbrNAn" alt=""><figcaption></figcaption></figure>

*Horizontal bar chart, ranked.*

Resources ranked by average peak sound level.

#### Average Sound Level by Weekday

<figure><img src="/files/p00YNMFdZMABno2aGxPK" alt=""><figcaption></figcaption></figure>

*Bar chart.*

Peak-noise averages by day of the week.

***

### Tab 2 — Data

#### Noise Data Table

<figure><img src="/files/SI5SLH4qIh1vif1guQFE" alt=""><figcaption></figcaption></figure>

*Sortable data grid.*

Minimum, maximum, and average ambient noise (dB) per resource.

#### Sound Data Table

<figure><img src="/files/MNSvJyK4OA1vkXdvMQP2" alt=""><figcaption></figcaption></figure>

*Sortable data grid.*

Minimum, maximum, and average sound level (dB) per resource.

Both tables support CSV, JSON, and PDF export.

***

### Tab 3 — Map

#### Sensor Map View

<figure><img src="/files/Yd5txfZecVP01kKje4ZP" alt=""><figcaption></figcaption></figure>

*Interactive geographic map.*

Buildings plotted on a world map, colour-coded by acoustic status.

***

### Tab 4 — Floor Heatmap

#### Acoustic Floor Heatmap

<figure><img src="/files/0bo3VtgDYroWSDZnWxw9" alt=""><figcaption></figcaption></figure>

*Colour-coded overlay on an interactive 2D floor plan.*

Each monitored resource appears as a heat point coloured by its current acoustic band.

*Use it to:* visualise where in the floor plan noise concentrates, supporting decisions on screening, partitioning, and zoning.

***

### Filters & Controls

* Building, Floor, Resource, Resource Type
* Date range with presets and custom ranges
* Granularity tabs on trend charts
* Metric switcher: Ambient Noise / Sound Level

***

### Tips

* Cross-reference high noise readings against the Occupancy dashboard. Persistent noise during low-occupancy periods often indicates a faulty sensor or persistent equipment hum.
* Use the Sound Level chart to investigate complaints about specific events — peaks are usually clearly visible.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.meetuma.ai/uma-knowledgebase/data-and-reporting/analytics-pro/dashboard/ambient-noise-and-sound.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.