Site Assessment Guide
This guide helps you navigate the conversations and decisions involved in preparing a site for Novant deployment. It covers the key topics you’ll need to discuss with building owners, facility managers, and IT teams before installation begins.
Building and Site Details
Every Novant project starts with basic site information:
Project / Building Name — used to identify the project across Novant. Choose a clear, consistent name early on, especially if you’re managing multiple buildings.
Address — Novant uses the site address to determine timezone and pull local weather data. Make sure the full street address including city is captured accurately.
Choosing a Node Type
Novant supports two edge node types. Your choice affects cost, site requirements, and what you’ll need from the IT team.
| Node Type | Best For |
|---|---|
| Virtual Node | Sites with existing infrastructure (PC, VM, or server) that can host a Docker container. |
| Hardware Node | Sites that need a dedicated, hardened device — or where no suitable host machine is available. |
Questions to ask the site team:
- “Where could I install a node to communicate with the BAS/BMS controllers?”
- “Are the building systems on one subnet, or are they segmented across multiple networks?”
Virtual Node Hosting
A virtual node is a Docker container that needs a host machine on the building network. Common options include:
- An existing PC or workstation
- A virtual machine provisioned by IT
- A dedicated device purchased for this purpose
Questions to ask the site team:
- “Can we host the virtual node on an existing machine, or should IT set up a VM?”
- “Would it be better to provide dedicated hardware for this?”
See Setting Up Your Virtual Node for deployment instructions once the hosting decision is made.
Network and IP Configuration
The edge node needs to be on the same subnet as the building automation devices it communicates with. Understanding the network layout early avoids connectivity issues during setup.
Static IP — a fixed address assigned manually. Common for servers and infrastructure devices that need to always be reachable at the same address.
DHCP — the network automatically assigns an available address when the device connects. Simpler to manage but the address may change over time.
Questions to ask IT:
- “Does this device need a static IP, or can it use DHCP?”
- “What subnet are the BAS controllers on?”
- “Are there VLANs or firewall rules that could block communication between the node and building devices?”
Outbound Internet Access
The edge node requires outbound internet access to connect to Novant. This is an outbound-only communication model:
- All connections are initiated from inside your network — the edge node makes the request.
- External systems cannot initiate connections into your network.
- The edge node connects to a single endpoint:
node.novant.io.
If the site requires traffic to pass through a proxy server, see Configuring an Outbound Proxy.
Questions to ask IT:
- “Can this device reach external endpoints over HTTPS?”
- “Does outbound traffic need to go through a proxy?”
- “Can you whitelist
node.novant.ioif needed?”
Identifying Building Systems
Understanding what systems are on-site and how they communicate determines your integration approach. The key things to identify are:
System type and vendor — what BMS, EMS, lighting, or metering systems are installed? The vendor and model affect which protocols are available.
Protocol — how does the system expose data? Common protocols include BACnet IP, BACnet MSTP, Modbus TCP, Modbus RTU, and OPC UA. The protocol determines how the edge node connects and whether additional hardware (such as a BACnet MSTP gateway) is needed.
System version — older versions of the same system may have different capabilities or protocol support. Check the version and any installed add-ons.
Questions to ask the site team:
- “What BMS is installed and what version is it running?”
- “What protocol does it use — BACnet, Modbus, or something else?”
- “Are there other systems (metering, lighting, energy management) that should be connected?”
See Supported Systems for a full list of vendors, models, and protocols Novant can connect to.