Network Basics

An edge node needs to communicate over your site’s network to collect data from building systems and send it to Novant. This guide covers the networking fundamentals you’ll need to have productive conversations with IT teams during deployment.

IP Addresses

Every device on a network has an IP address — think of it as a mailing address that lets other devices find it. There are two ways a device can get one:

• Static IP — a fixed address that’s manually assigned and never changes. This is common for servers, controllers, and infrastructure devices that need to always be reachable at the same address.

• DHCP — the network automatically hands out an available address when a device connects. This is simpler but the address can change over time, which may cause issues if other devices need to find it reliably.

For edge nodes, either option works. Your IT team will have a preference based on how they manage their network.

Questions for IT:

• “Should this device use a static IP or DHCP?”
• “If static, what IP address, subnet mask, and gateway should I use?”

Subnets

A subnet is like a neighborhood inside your network. Devices in the same subnet can talk to each other directly. Devices in different subnets need a router to pass traffic between them — and in many buildings, that routing may not be configured by default.

The edge node needs to be on the same subnet as the building automation devices it’s collecting data from. If they’re on different subnets, IT will need to set up routing between them, or you may need to install an additional edge node on each subnet.

Questions for IT:

• “What subnet are the building automation devices on?”
• “Can the edge node be placed on that same subnet?”
• “If not, can routing be configured between the subnets?”

VLANs

A VLAN (Virtual LAN) is a way to separate traffic on the same physical network into isolated groups. Many buildings use VLANs to keep building automation traffic separate from corporate IT traffic, guest Wi-Fi, and other systems.

If the site uses VLANs, the edge node needs to be placed on — or given access to — the VLAN where the building devices live. This is something IT configures on the network switch.

Questions for IT:

• “Are the building automation devices on a separate VLAN?”
• “Can the edge node be added to that VLAN?”

Where to Install the Edge Node

The edge node must connect to the same network as the devices it needs to communicate with. This means the building automation network, not the general office Wi-Fi or guest network.

Common installation locations:

• An open Ethernet port near the building automation equipment
• A network switch that connects to the building automation network
• A virtual machine that IT has configured with access to the correct network

Your IT team can tell you the best location based on how their network is set up.

Questions for IT:

• “Which network should the edge node connect to so it can reach the building automation devices?”
• “Is there a specific port or switch I should use?”
• “Does the node need to be on a dedicated VLAN?”

Multiple Networks

Some sites have separate networks for different systems — one for building automation, one for lighting, one for metering, and another for corporate IT. If the systems you need to connect to are on different networks, you have two options:

1. Ask IT to set up routing between the networks so a single edge node can reach all devices.
2. Install an edge node on each network. Novant can aggregate data from multiple edge nodes into a single project, so this is a common approach for segmented sites.

Questions for IT:

• “Are the building systems all on one network, or spread across multiple?”
• “Can routing be set up between them, or should we plan for a node per network?”

Firewalls and Ports

A firewall controls what traffic is allowed in and out of a network. The edge node needs outbound access to reach Novant — it connects to a single endpoint (node.novant.io) over HTTPS (port 443).

The edge node does not require any inbound ports to be opened. All connections are initiated from inside your network — external systems cannot reach in.

This outbound-only model is a common pattern for IoT and building infrastructure devices, and is generally straightforward for IT teams to approve.

Questions for IT:

• “Can this device make outbound HTTPS connections to node.novant.io?”
• “Are there any firewall rules that would block outbound traffic on port 443?”

If outbound traffic must pass through a proxy server, see Configuring an Outbound Proxy.

Identifying Your Protocol

Different buildings use different protocols for device communication. BACnet and Modbus are the most common. The protocol determines how the edge node connects to the building system and may affect hardware requirements — for example, BACnet MSTP (serial) requires a gateway to bridge to the IP network.

If you’re not sure which protocol is in use, check the system documentation or device labels. Your building automation contractor or BMS provider can also confirm.

Questions for the site team:

• “Is the building automation system using BACnet, Modbus, or another protocol?”
• “Are the devices communicating over IP or serial connections?”
• “Is there existing documentation or a points list for the system?”

See Supported Systems for a full list of protocols Novant supports.