--- title: Namespace description: The Namespace is a single browsable tree of everything your Organization models: Locations, the Assets inside them, and the points those Assets read from. Filter it, select a node, and inspect properties, live values, relationships and active Alarms. source: https://documentation.controlcomtech.com/platform/namespace --- # Namespace The Namespace is one browsable tree of everything your Organization models: Locations at the top, the Assets that sit inside them, and the points each Asset reads from. Select any node and the panel beside the tree describes it, shows what it is reading right now, and lists what it is connected to. > **Workflow Stage: Analyze** ## Overview Open **Visualization → Namespace** in the sidebar. The screen is split: a resizable tree on the left, an inspector on the right, and a filter toolbar across the top. Most other screens in ControlCom Connect answer a question about one kind of thing. The Devices list is about Devices, the Alarms page is about Alarms. The Namespace is the opposite: it is the single place where the whole model is laid out in the shape a facility engineer already thinks in, from a campus down to an individual reading, so you can find a point without knowing which Device happens to publish it. ![The Namespace page in ControlCom Connect, showing the location and asset tree on the left and the inspector on the right](https://documentation.controlcomtech.com/images/small-areas/01-namespace-browser.png) *The Namespace: the model tree on the left, the inspector for the selected node on the right* ## How the Tree Is Built Nothing on this page is configured directly. The tree is assembled from what you have already modelled elsewhere, so it changes as the model changes. Locations form the roots, nested by their parent Location, so a campus with two buildings under it appears as a campus node with two children. Inside each Location sit the Assets assigned to it, nested by their own parent Asset, which is what lets a chiller plant contain its chillers and each chiller contain its pumps. Under an Asset come its points: the Device Variables bound to that Asset, plus any Virtual Variables calculated from them. Assets that have no Location yet are still reachable. They collect under a synthetic top-level node named **Unassigned**, which is a useful list to keep an eye on while a deployment is being built out: anything sitting there has not been placed on the site map. Every node also carries a namespace path, the readable trail of names from the root down to that node, separated by slashes. The inspector prints it under the node title, and it is the quickest way to confirm you are looking at the right instance when several Assets share a name. ## Narrowing the Tree The toolbar above the tree combines a search box with a row of filter chips, and the count on the right reports what survives: how many Locations, Assets and points are currently in view. **Search namespace** matches node names as you type. Search and the filter chips are narrowing filters, so when they cut the tree down to a manageable size the matches are revealed automatically rather than leaving you to expand branches by hand. **Show** switches how deep the tree goes: **Everything**, **Locations & assets** (hides the individual points), or **Locations only**. Use it to step back to a site overview when the point-level detail is noise. **Alarms** filters to nodes carrying an active Alarm. The chip offers **Any active alarm** as a single click, or a specific severity when you only want the critical ones. The remaining chips are added from the **+** button as you need them, and each stays visible while it holds a value. **Type** filters by Asset Type, **Classification** by Asset classification, **Location** to a single site or building, **Unit** to points measured in a given unit such as kW or V, and **Points** to Enabled or Disabled Variables. **Clear all** resets the toolbar. Because filters combine, a question like "which points in the North Tower are measured in kW and currently in alarm" is three chips rather than a query. ## The Inspector Selecting a node fills the right-hand panel. What appears depends on what you selected. For an Asset the **General** tab lists its type, classification, how many Variables it has and the Location it belongs to, along with its description. Below that, **Relationships** draws the Asset in context of the typed relationships you have defined, as a **Graph** or as a **List**, and any node in the graph can be opened in the tree. Last comes **Device variables**, a live preview of the Asset's points with their current values, so an Asset page doubles as a small readout of the equipment it represents. The pencil icon in the header opens the Asset for editing, if your role allows it. For a Device Variable the **General** tab covers the practical detail: data type, unit, MQTT topic, classification, whether logging is enabled and whether the point is active. Above the tabs, a data browser charts the point's history, so you can go from finding a reading to reading its trend without leaving the page. Virtual Variables show the same shape plus the expression they are calculated from. Assets and Device Variables also carry an **Alarms** tab holding the active Alarms attached to them, with a dot on the tab when there is something to look at. From an Alarm row you can jump straight to the Variable that raised it. Locations show a shorter card: the node type and its coordinates. ## Sharing a View Both the selection and the filters live in the URL. Selecting a node sets an `entity` parameter, and each filter chip writes its own parameter (`q` for the search text, `severity`, `type`, `classification`, `unit`, `location`, `points` and `show`). That makes a Namespace view something you can send to someone. Filter to the generators in alarm, select the one you want a second opinion on, and the link you copy from the address bar opens the same tree, filtered the same way, with the same node selected. ## Related Workflow Stages The Namespace only shows what earlier stages have produced. Points appear once Devices are Connected and their Variables are Collecting, and the tree's shape comes from the Locations and Assets you have modelled. If a piece of equipment is missing here, it is missing from the model, not from this page. From here, the Data Explorer is the next step when a single point's history is not enough and you want to compare several ([Data Explorer](https://documentation.controlcomtech.com/platform/explorer)). When a view is worth keeping in front of people rather than looking up, rebuild it as a dashboard in the Visualize stage ([Dashboards](https://documentation.controlcomtech.com/platform/dashboards/overview)) or as a one-line drawing ([Diagrams](https://documentation.controlcomtech.com/platform/diagrams-detail/overview)).