Home / For IT Teams
For IT Teams
BERT and Your Network
What your IT team needs to know to approve a BERT system: how it connects, what it keeps in the cloud and who can see it, what happens in an outage, and the checklist we work through with you before anything ships.
BERT on Your Network
BERT connects the way a well-behaved network device should: no customer-provided server, and no inbound ports to open.
How BERT Connects
BERT controllers (the Smart Plug 110 AP and the Inline Series) join your existing Wi-Fi network like any other client. Only the BERTBrain Gateway needs a fixed IP address: a static private IP or a DHCP reservation both work. BERT controllers get their addresses automatically by standard DHCP, with no special DHCP options, DNS or time server needed. The Gateway runs BERTBrain, cloud-connected or on-premises as approved for your project, and no customer-provided server or virtual machine is needed.
Outbound Only
Every connection starts at the BERTBrain Gateway. Its internet connections are outbound only: there are no inbound ports for your IT team to open and no port forwarding.
Wi-Fi Security
BERT controllers support WPA2-PSK and WPA2-Enterprise (PEAP/MS-CHAPv2) on 2.4 GHz and 5 GHz, 802.11 a/b/g/n networks. A dedicated or segmented IoT network is commonly recommended, so your devices stay visible in your own network tools and under your IT team's control.
Software Updates
Controller firmware updates arrive over the air, through the Gateway.
If Wi-Fi or the Internet Goes Down
Control keeps running: each controller stores its own schedule, and the override at the device still works. Each controller keeps a 14-day log and sends it once the connection returns. Remote visibility and remote changes in BERTBrain pause until the connection is back, and any BERT Connect link to a building automation system pauses too; your BAS keeps running as usual. Is the gateway a single point of failure? →
Computers, Servers and Network Equipment
BERT doesn't cut power to computers that need to stay on. At installation, desktop computers go on an uncontrolled outlet, while monitors, docking stations and other desk equipment stay on the controlled schedule. Servers and core network equipment are not controlled.
Planning a Network Change?
Tell your BERT project team before you change your network name, password or certificate. Controller Wi-Fi settings need to be updated first so devices stay connected.
Your Data and Who Can See It
In a cloud-connected system, your site's setup (which controller runs which device, plus your schedules and settings) and your energy and savings records are backed up in the cloud. It's equipment, schedule and energy data, plus your designated users' sign-in details if you choose to include them; never student data. Only your organization and BERT have access, and no one else gets access without your organization's authorization.
Your designated users sign in to BERTBrain with role-based user accounts. Their sign-in details (names and email addresses) don't have to be part of the backup, but we recommend including them because it makes restoring a replacement gateway simpler. In a cloud-connected system, if a gateway ever needs replacing, BERT can promptly ship a replacement and restore your setup on site without reprogramming your controllers.
Prefer no cloud connection? An on-premises-only setup is available. Your controllers work exactly the same, but BERT can't keep a backup or quickly restore a replacement gateway, it can't alert your team remotely, and your designated users can reach BERTBrain only from your own network. Software updates and backups are done manually with your IT team.
How does BERT connect to our network, and what does it keep in the cloud? →
IT and Network Checklist
BERT is designed to fit an owner-approved network architecture. BERT works with your IT team before anything ships, so the network plan is settled up front.
What Your IT Team Provides
- Approval of the network approach (for example, a segmented IoT network)
- Wi-Fi coverage where controllers will be installed
- For the Gateway: a fixed private IP address (static or DHCP reservation) and its network settings
- Outbound internet access for the Gateway
- A secure way to share network settings with BERT
How BERT Works With IT
- An IT readiness meeting early in the project, before equipment is staged
- BERT configures and tests every controller for your approved network at its staging facility before shipment
- When included in the project scope, a network verification unit lets IT confirm connectivity on the intended network before broad deployment.
- Network credentials are never placed in general closeout records
- Authorized partners and project teams can get the BERTBrain Gateway Setup Guide, which lists current endpoints and ports, through the Partner Portal
BERTBrain at a Glance
- Cloud-connected or approved on-premises deployment
- Web browser access
- Role-based user accounts
- Updates: automatic in the cloud; manual on-premises
- Standalone by default; no BAS connection or BAS changes required
- Optional BERT Connect (BACnet/IP) or REST API integration, scoped per project
Common IT Questions
- How does BERT connect to our network, and what does it keep in the cloud?
- Is the gateway a single point of failure?
- Why does BERT use Wi-Fi instead of its own wireless system?
- How does BERT address network security?
- What happens if our Wi-Fi or internet connection goes down?
- Which devices are generally not controlled by BERT?
- Does BERT have to integrate with our building automation system?
- All Questions →
Designing or Specifying BERT?
The guide specification, controller ratings, data sheets and design limits are on the page for engineers and specifiers.