Project Checklist
Before you begin configuring a new Novant project, it helps to collect a few key details upfront. This guide outlines the initial questions to ask and information to gather—so you can streamline setup, avoid rework, and get your project up and running faster.
| Item | Comment |
|---|---|
| Site Info | |
| Project / Building Name | |
| Address | Every project requires a city |
| Deployment Info | |
| Node Type | Virtual or Hardware Node |
| Hosting Environment | For virtual nodes only |
| Static vs DHCP | Needed for hardware node setup |
| Internet Access | Required for Novant node to connect |
| System Integration | |
| BMS Type(s) | e.g., Tridium, Distech, Reliable |
| Protocol(s) Used | e.g., BACnet IP, Modbus RTU, MQTT |
Project / Building Name
Novant works based on projects, starting with the building name will make filtering, searching and managing portfolios much easier in the future.
Address
Within Novant, timezones and weather are linked to the site address. Getting the right information will affect the results of both of these services.
Virtual Node or Hardware Node
Choosing between a Virtual Node and a Hardware Node is important for both cost and site requirements. Each option has different implications, and your IT team will need different information depending on which you select.
Questions for the site team:
“Where could I install this Hardware Node to communicate with the BAS/BMS Controllers?”
“Are the networks on one subnet? If I install my node in location X will I be able to communicate with the meters and BAS?”
If Virtual Node - Hosting Environment
A Virtual Node is a Docker image (a packaged piece of software) that needs to run on some hardware. It can be installed in different ways depending on what makes the most sense for your site:
- On an existing PC (e.g., a supervisor’s workstation)
- On a virtual machine set up by your IT team
- On a dedicated device you purchase for this purpose
This flexibility means Novant can fit a wide range of site setups and IT requirements.
Questions for the site team:
If you’re not sure where to install the Virtual Node, you can ask:
“Can we host the Virtual Node on an existing PC, or should IT set up a virtual machine?”
“Would it be better for us to provide dedicated hardware for this?”
Static vs DHCP
Every device on a network needs an IP address. There are two main ways to get one:
Static IP: A fixed address that never changes, usually set manually. Commonly used for servers, printers, or devices that need to always be reachable at the same address.
DHCP: An automatic system where the network assigns an available address when your device connects. This is easier to manage and is used for most laptops, phones, and day-to-day devices.
Understanding the IP Address helps with the architecture design, we need to be on the same subnet as the devices we want to speak with. You can see more information about subnets below.
How to ask IT about it:
If you’re not sure which you need, a simple way to ask your IT team is:
- “Does this device need a static IP, or can it use DHCP?”
- “Can you assign me a static IP if I need consistent remote access?”
Outbound Internet Access
Outbound internet access might raise concerns at first, but it’s a standard and secure requirement for modern building infrastructure. Novant devices use an outbound-only communication model designed to prioritize network security. This means:
- All connections are initiated from inside your network - the device makes the request.
- External systems cannot initiate connections into your network or the device.
- Each device connects only to a single endpoint: the Novant Cloud.
BMS Systems
Novant can connect to many systems in a building. Understanding what system you want to connect to earlier will reduce risks in terms of setup, compatibility and additional resource potential i.e BACnet MSTP gateways.
Our most common connection type is through Building Management Systems (BMS). The type of system and the version greatly changes the methods we would need to connect. Combining this with the architecture will give a clear path of what the available methods and limitations are.
For all system types it’s very important to also find out the available protocols, as shown below.
Some examples of system types we see are:
| Vendor | Model | Type |
|---|---|---|
| Siemens | Desigo CC | BMS |
| Siemens | Apogee | BMS |
| Siemens | Insight | BMS |
| Schneider Electric | Struxureware | BMS |
| Niagara | N4 | BMS |
| Niagara | AX | BMS |
| Trend | 963 | BMS |
| Trend | IQVision | BMS |
| Johnson Controls (JCI) | Metasys | BMS |
| Johnson Controls (JCI) | Verasys | BMS |
| Honeywell | EBI | BMS |
| Automated Logic | WebCTRL | BMS |
| Alerton | Ascent Compass | BMS |
| Distech Controls | Eclypse | BMS |
| Schneider Electric | Power Adviser | Energy Management System (EMS |
| IBM | Envizi | Energy Management System (EMS) |
| Siemens | SIMATIC Energy Manager | Energy Management System (EMS) |
| Lutron | Athena | Lighting Control |
| Lutron | Vive | Lighting Control |
| Crestron | Zum | Lighting Control |
As you can see some vendors have many models, this can change the requirements. Also to keep in mind depending on the version and sometimes the “add-ons” for these systems you may run into different capabilities.