Understanding nodes

You can view your Nodes in two ways: as a Node Table for detailed information or as a Node Map for a visual overview.

Node properties

  • Name: The name of the organisational unit (e.g., "Global Company," "Australia," "Sydney CBD").

  • Type: Defines the nature of the organisational unit (e.g., "business," "region," "facility").

  • Parent Node: Indicates the hierarchical relationship, showing which larger unit this node belongs to (e.g., "Global Company" is the parent of "Australia" and "USA").

  • Country: The country where the organisational unit is located.

  • Region: The specific region or state within the country.

Tips for Climate Reporting Specialists and Business Managers:

  • Emissions Boundaries: The Node Map provides a clear visual of your organisational boundaries for GHG Protocol reporting. Each node can represent a distinct operational control or equity share boundary.

  • Data Aggregation: Understanding this hierarchy is crucial for aggregating carbon emissions data from individual facilities up to regional and global levels for comprehensive reports.

  • Report Generation: When generating compliance reports, you will often select specific nodes or branches of this map to define the scope of your report.

Node Map

The Node Map offers a visual representation of your organisational structure, showing the relationships between different entities. This is especially helpful for climate reporting specialists and business managers to quickly grasp the scope of their emissions boundaries.

A representation of a business with 2 facilities, 1 project, and a business branch called "ABC Doors"

Step-by-step Guide: Understanding Your organisational Structure via the Node Map

  1. From the Admin Panel, ensure the "Nodes" tab is selected.

  2. Click the "Node Map" sub-tab.

  3. Observe the visual hierarchy:

    1. The top-level node, typically your "Global Company," represents the overarching entity.

    2. Lines extending downwards (in Vertical Layout) or sideways (in Horizontal Layout) connect to child nodes, which could be regions or countries (e.g., "Australia," "USA").

    3. Further branches lead to facilities or specific offices (e.g., "Sydney CBD," "Melbourne Office," "New York").

By effectively configuring and understanding your Nodes, you lay the groundwork for accurate and streamlined carbon emissions data input and compliance report generation within NetNada.

Last updated